Windows Recovery Drive not working after using NTLite

NoTRite

Member
I just finished making my windows ISO and installing, only to find out that the recovery drive I made with it afterwards won't work when I test it. When I boot up from the recovery drive and select Troubleshoot => Recover from a Drive => Just remove my files => Recover, it will go up to 60% and then throws this error:

Code:
Reset this PC:

There was a problem resetting your PC. No changes were made.

Afterwards, I discovered that it apparently made a lot of changes, and Windows won't even show up in my BIOS anymore. However, when I reinstall, the 4 default windows partitions from my previous install still show up in the windows installer and I have to manually delete them.

I then tried installing "vanilla" windows and the recovery drive I made with it worked. This means that I know my NTLite settings are the culprit.

Since Windows is giving me literally zero information, I have no idea what to do. This is a brand-new installation after using NTLite on the install iso. Attached is the settings file I used, and I did nothing else after installation aside from making the recovery drive. The source image used was Windows 10 1803 Professional.

Could someone please tell me what component or service I need to re-enable to get recovery working? This is the last thing I need before I'm finished with this install.

Thank you!
 
Thanks for reporting and your patience, missed this one.

Confirmed the issue, it will require more than a quick Sunday look, will let you know when I have more info (max a day or two).
 
Thanks for reporting and your patience, missed this one.

Confirmed the issue, it will require more than a quick Sunday look, will let you know when I have more info (max a day or two).

Thanks for taking the time to reply even though it was the weekend!

I think I tracked down part of the issue to the Workstation service, which can't run in the resulting image. To get the workstation service running, I have to enable, at minimum:

Code:
Network > File Sharing Support > TCP/IP NetBIOS helper > Computer Browser > SMB v2

Within NTLite, the notes say only the Computer Browser is necessary for the Workstation service, with no mention of the SMB v2 feature being necessary.

I'm going to try replicating the issue in virtualbox with an image that includes SMBv2 later.



Edit: Though, TBH, I'd prefer if I could leave the SMB v2 feature out...
 
Last edited:
Computer Browser component is the Workstation service.
This is its description "Includes Workstation service. In order to use file shares, these services are required."
Let me know if you would suggest a rename or something to make it more clear.

Finished the Reset PC issue assessment.
Unfortunately it requires all of WinSxS files to be kept. There are some good news:
- you can use any full Win10 ISO, preferably pre-updated, to refresh the PC; just start setup.exe from the ISO root and follow the prompts (similar to Recovery). Should have told you this from the get-go, forgot about it.

- As for when you don't have an ISO and want to have it built-in the OS, I'll add the Compatibility option "Recovery Reset support" to the next version. That will keep the files in WinSxS during removals, however resetting such PC will return components as well (still need to test that to confirm).
To some extent that is a nice option to have for running easier tests when removing more and more. Similar can be had with Host Refresh option in the tool.
Only negative side of that compatibility option is that ISO size will not go down, it will look like nothing is removed, but actually all of the deployed files and registry are, as always - size is kept by the WinSxS content.
 
So "Recovery Reset Support" will be included on Tuesday? You're Amazing!!!! :D

Also, regarding the workstation service... I can see the workstation service in services.msc when I use an iso that only includes Computer Browser, but I can't start it. I can only start it when I enable SMB v2 as well.

Were you unable to replicate the issue?

Or are you saying that when I enable Computer Browser, it's ok that the workstation service doesn't work, because it's technically included somewhere even though it's broken?
 
Yeah, reset PC compatibility worked out.

Gonna delay release for one day, would like to fix, or connect SMB 2 with Computer Browser, just confirmed the issue.

Thanks!
 
Yeah, reset PC compatibility worked out.

Gonna delay release for one day, would like to fix, or connect SMB 2 with Computer Browser, just confirmed the issue.

Thanks!

I'm glad I could help! ;)

Any news yet? I'm really looking forward to your next release!
 
Currently changed too much for the Win10 RS5 fix, and when I do that I tend to test it for a few days with a handful of trusted users before releasing.
So it is now delayed until Tuesday, while checking on other reports as well.
I could send you a pre-release version with that functionality whenever you want, just ping me.
 
Let me know if the issue is resolved for you with the build 6500+, once the Reset PC compatibility is enabled before any initial removals.
Thanks.
 
Back
Top