Windows Hang After NTLite Finish

H

HosseinMoradi

New Member
after NTLite finish applying and request a reboot, when i press yes, on 80% of times, windows will kinda hang there or on restart screen.
after forcing reboot, randomly, the taskbar and start menu will not respond anymore.

to reproduce the bug create an offline windows 10 using offline present.
install on VirtualBox.
apply the online present.
 

Attachments

  • Test Offline.xml
    55.4 KB
  • Test Online.xml
    2.9 KB
Thanks for the report, will try it tomorrow, tried the online one alone and no issues, so I do indeed need that exact combo it seems.
 
nuhi said:
Thanks for the report, will try it tomorrow, tried the online one alone and no issues, so I do indeed need that exact combo it seems.
Click to expand...
yes, i have a more compacting offline present that this online present don't have this issue with.

just remember the problem is random on the online present, if it didn't fail on the first run, use the same offline image and try it again.
 
Hi,

unfortunately cannot replicate, here are some findings which may clue us in:

- I'm using VMWare instead of VirtualBox, driver protection kept
<c>driver_c_memory.inf</c>
<c>driver_lsi_sas.inf</c>
<c>driver_memory.inf</c>

I would keep Memory related components regardless of the machine.
Also make sure to install Guest VM tools/drivers before continuing after setup, if wasn't already.

- Since it's just 10 components, should be easy to retest using snapshotting in a VM and let me know exactly which component is it
I suggest it might be one of these:
<c>appreadiness 'App Readiness'</c> (maybe it needs time after install to propagate some app readiness, start menu is also an app)
<c>clipsvc 'Client License Service (ClipSVC)'</c> (related to Windows activation, similar to above, or maybe not even removable)
<c>tempcache 'Cache and temp files'</c> (it might delete something temporary that the machine is currently working on)
But of course if not, try the others.

- Try VMWare Player/Workstation as the last resort, as we might be hunting a VirtualBox bug/driver dependency.
It's just these 10 removals do not ring anything special to it, if it was drivers, maybe.
If by a slim chance you confirm that it works with VMWare, then I'll setup a VirtualBox setup and give it another try.

Thanks.
 
did a lots of testing and here is the findings:

1: first, i had the problem on my PC a few times, lately i test the setup in VirtualBox and if OK will do it on my PC.
so the problem is not VirtualBox bug or related.

2: the problem is system semi hang, unresponsiveness and refusing to restart or shut down

3: keeping blow components didn't have any affect on the problem.
<c>driver_c_memory.inf</c>
<c>driver_lsi_sas.inf</c>
<c>driver_memory.inf</c>

4: installing VirtualBox driver lowered the possibility of the problem a lot (4 out of 5 didn't fail), but still happened. and since i do the NTLite on my PC before installing any driver (because i what a minimal sized image of it), i suggest you do the testing without any driver installed.

5: i wasn't able to setup the image in VMWare Player and since the problem isn't VirtualBox related, i didn't do any testing in VMWare.

6: the tokenbroker 'Web Account Manager' component is the cause.

7: stopping the 'Web Account Manager' service before NTLite, fixed the problem.

8: in my testing stopping the service using 'sc stop tokenbroker' inside a CMD file, caused the problem randomly a few times.
 
did a few x86 image test, here is the findings:

1: the attached offline present have the same problem, the x64 bit version of it didn't.

2: the x86 version has less randomness and almost every time has the problem.

3: stopping the 'Web Account Manager' service before NTLite, didn't fix the problem. i had to disable the service, reboot, then apply NTLite.
 

Attachments

  • Test Offline Minimalist x86.xml
    55.9 KB
Hi,

thanks for the extra info.

So, as far as I see it:
- Web Account Manager needs to be disabled and rebooted before removed - not sure if this can be fixed, probably the service is holding something from being directly removed
- x64 version almost never has the problem, that explains why I could not replicate

I'm not sure what I can do there, keep the component if it creates issues being removed, or disable and reboot before removing it.
If more people would report this, I might come up with a delayed removal on reboot or something, but it's not worth the trouble, nowhere does it state that all components should be removable on all systems without any downsides - in this case disabling one service and rebooting is hardly a big deal.
 
You must log in or register to reply here.
Back
Top