Strange error messages - Would different explanations help?

pmikep

Active Member
During the past few days I've gotten some new (to me) error message using NTLite. (1.8.0.7070.) I'm not very good at keeping my Journal while I 'Lite. So I doubt that I can recount all the steps that caused these messages. Mostly the point of this post is to query whether differently worded messages would tell the user more.

So, for example, while doing something with Win8.1, I got this message about "handles."

The handle message q.jpg

Is a "handle" a "name," like in CB-Radio slang?

Then I got this message.

image has been damaged.jpg

I don't understand what an "offline servicing failure" is. Is there such a thing as an "online servicng failure"?

Then when I started to work on a Win7 image, I got this message:

component store is corrupt message.jpg

When I saw the word "store," I immediately thought of the Store in Win8.1. But since this was Win7, I knew the message couldn't be referring to the Windows' Store.

I am guessing that it has something to do with the Components in my Win7 iso.

Last, I got another message after this about "handles" again.

The the handle is invalid message Win7.jpg

I don't have a clue what this is telling me.

BTW, these last two error messages threw Windows and NTLite into a deep hole. I had to jump through a lot of hoops to get NTLite working again. And, IIRC, I saw NTLite do an automatic cleanup of some directories.

So kudos to nuhi for making NTLite more robust. I remember that it was a year or two ago that we were gettting into some strange states with NTFS links, where it was nearly impossible to delete the Mount Directory.
 
Thanks for the report, but without the actual steps to get to that state, it can be anything.
Next time when you get that handles error, please don't click anything, just copy %temp%\ntlite.log and the preset that you used.
Then cancel processing, unmount the image, reboot, recopy fresh image, and retry using the same preset. If you then have the same, send those files to me.
If it doesn't happen again, then do you have some antivirus, including Defender that is constantly scanning? Those can seemingly random take hold of files being edited.
To check that, open Task Manager and sort by CPU usage while NTLite is processing.
 
Thanks. I do not have any AV (nor Defender) on my computer. (gasp!) I rely, in part, on NTLite removals to help keep me safe from attack. (And I run all my browsers in a Comodo Virtual Sandbox.)

If there is a next time that I get these error messages, I will do what you say.
 
Back
Top