So was the problem only in the WinHttrack.exe shell, or in 
the underlying httrack.exe too?  I recall that that 
previously it appeared not to be happening when you were 
using the httrack.exe command line version.  

Anyway, I'm glad something has been found.  The other 
question is would the mentioned 'bad' writing that caused 
heap problems have corrupted any specific downloads from 
sites?  Anything specific to look for?