Shell Hardware Detection is needed for printing. And with latest printersoftware from 2014 you may consider keep RPC locator for backwards application compatibility. Preset still show you don't use Compatibility a least for printing. If you've same problems with Compatibilities checked from the related problems you discover- why not post that preset?
Keeping Shell Hardware Detection - Autoplay is uncheckable as subpoint - how can you miss that?
It's a little hard to find out if you're having selfmade problems or not - your post state you're unable to print and now you state you're able to print.
About the WM i don't know as i don't use Hyper-V.
But same time it's needed for Printing - and you maybe will be window(s) free.
Deeply frustrating when you seem to have tried it all - you can download an updated image from here (Check download additional edtions and choose Enterprise as you use) - then you only need the latest .Net framework update. Have even had issues before when I started with 19041.1 image. With all the issues you describe in various entries I would consider starting all over again and installing a fully updated Windows 10 - installing the printer driver and checking everything works (if not it might be a hardware issue)!?! Take a backup and quietly identify which NTL points I can remove before it does not work as intended. It takes time but usually fixes the problem unless it is a hardware or software issue that is not up to date according to Windows 10 requirements specifications.
Wise words:
If it goes as intended, it is always oneself who is the smart one - but always an outside problem if what one does does not work as intended.
Answered in PM.Thanks, but could you tell me the difference between integrating all updates on a 19041.1 build and installing Windows and downloading and installing the latest build? The problem is that I've been having problems since I started using NTLite back in 2017 and I've been removing one component at a time.
Answered in PM.
Please confirm everything is working on a clean updated install (not basic image 19041.1). You're still walking around in a circle to find a corner in manner of speak!
Nice to hear if you've solved the issues.
You’re aware that in latest NTL 2.0.0.7820 following components got upgraded:
Components: Renamed IE HTML Viewer to HTML Viewer (Legacy) and moved to System components
Components: Renamed Edge HTML Viewer to HTML Viewer and moved to System components
I’ve removed both Internet Explorer 32 and 64 bit but keeping both HTML Viewer (Legacy) 32 and 64 bit incl. JScript (as they all get Locked by Compatibility: Recommended - except JScript) and don’t have any printing or scan issues over network (Using Epson ET-3700).
View attachment 4578
HTML Viewer gets Locked by Compatibility: Recomended and OOBE
View attachment 4579
If you use Compatibilities, the necessary components will be locked, of which Recommended and OOBE should be a minimum plus of course other components you know you'll need and therefore keep.
Microsoft released an update on Monday 5001567 to address an issue that causes windows 10 to crash when trying to print.