Windows Updates Not Working Post-NTLite Modding

B

BrokenDaily

New Member
Long ago back when I was on an HDD only setup, I was told to refresh to full, boot up ntlite, and do the preset I had set to remove crap I didnt need. After that, I could install CU's perfectly, get whatever it needed to update as is, then run ntlite again and never have to worry about doing too many refresh/update installs of windows 10, well that changed

I have since updated my setup to an SSD/HDD setup (SSD has OS, HDD holds everything else), and aimed to do the CU update then ntlite modding again, but windows is now telling me "yeah, thats not happening"; now I just want to know, besides updating a windows 10 iso with the CU's, SSU, and the other updates, how I can update my computer without burning through the lifecycle of my SSD so fast since now I have to worry about putting too much data onto an SSD that might die on me with no recoverability after thefact
 
Do a host refresh this time, and report a preset which broke Windows Update, I'm very interested in fixing it.

Thanks.
 
it'll take a while; the Windows 10 OS on my SSD had a total failure, wouldn't boot, so I have to re-download EVERYTHING I lost; thankfully I set the secondary HDD to hold everything usually on the main C: drive (desktop, videos, documents, etc...), plus the fiber optic internet we got will ensure I can get everything shortly

its the configuring everything back to what it was that's going to be a pain, so standby for now
 

Attachments

  • Main Preset (Windows10).xml
    23.9 KB
alright, I used ntlite to integrate all the needed windows updates into the win10 iso and clean installed it back on my computer, back to the SSD/HDD setup I had before, so im running windows 10 with it on default settings for now, hope my preset gets debugged soon, would very much like to trim all the junk I dont want off of windows 10 again
 
Thanks, sorry for the inconvenience.
OK, tried your preset on the 1903.356. After installing it, installed latest servicing stack and CU, at this time those are KB4528759 and KB4532695.
Used latest NTLite (build 7290), and saw no issues, so you should be safe, but read the next first.

Remember that you have to run Remove Returns tool after updating reboots, to clean the leftovers returned by the CU - doesn't take long and doesn't require an activation if there is an internet connection.
Will automate that after automating the tool self-updating first, in a case an urgent fix is needed.

Let me know if you ever stumble on this issue again, try to save aside any subsequent changes, be it REG, DISM script or NTLite, so I can replicate the situation if an update ruins it again. Windows itself is not flawless in this regard, you can read many horror stories online without NTLite, but we can not rely on it being the main cause, of course.

Note that it matters which NTLite version made the initial ISO, so if you see something around Windows Updating is listed as fixed in the changelog in a newer versions of the tool, it is recommended to Host Refresh using that updated version before you stumble on any issues.
To reduce stress around this, try using (free) backup solutions. I started backing up before updating - takes around 3-5min diffential backup to a network share, but still haven't had issues last 3-4 months, ready if any pops up.

Btw that reminds me, I see you use a lot of REG files, I haven't tested with those as they are not part of the preset.
Just make sure no services are disabled or entries removed with those.
 
Not really related, but FWIW, I have had problems installing later updates on two Win7 boxes after NTLite. To make a long story short, I had to go back and Refresh to Win7+SP1 only. From there I could install the latest updates.

I don't know if my problem had something to do with 'Liting, or if it was a problem caused by MS and their Service Stack changes . (Since both computers had been 'Lite'd, I don't have an un'Lite'd control to test.)
 
So I had a macrium reflect backup of my computer just in-case this ntlite'ing messed something up, and I updated ntlite to the latest stable released and live edited the junk off of my win10pro setup; did a shutdown and reboot, and the only problem I had was an error box that boiled down to AMDRSServ.exe opencl.dll missing. I did a repair install of the amd software for my rx 570 video card and its gone, but just in-case im making another reflect backup for my ntlite modified system

basically the last time this happened, it was a failed CU update to get past the 592 build number, then reinstalled the amd software, then a restart and suddenly boot device error; dism, sfc, and chkdsk report no problems, so for now, I guess its fixed, but I won't know until the next CU update and that will be a while
 
BrokenDaily said:
So I had a macrium reflect backup of my computer just in-case this ntlite'ing messed something up, and I updated ntlite to the latest stable released and live edited the junk off of my win10pro setup; did a shutdown and reboot, and the only problem I had was an error box that boiled down to AMDRSServ.exe opencl.dll missing. I did a repair install of the amd software for my rx 570 video card and its gone, but just in-case im making another reflect backup for my ntlite modified system

basically the last time this happened, it was a failed CU update to get past the 592 build number, then reinstalled the amd software, then a restart and suddenly boot device error; dism, sfc, and chkdsk report no problems, so for now, I guess its fixed, but I won't know until the next CU update and that will be a while
Click to expand...
Interesting, the opencl.dll is in rdvgwddmdx11.inf component, tied to RemoteFX - didn't know AMD driver needs it, must add that to description once confirmed.
Try keeping that in the future, or add opencl.dll in Components - toolbar - Compatibility, right-side protected file list.

Let me know if you do not remove RemoteFX and that INF, then I would be interested in a preset and method of removing the file - make sure the file is not at C:\Windows\System32\opencl.dll when AMD reports it, but mentioned components were kept.

Thanks.
 
According to some in the BlackMagic Resolve forum, opencl.dll is necessary for Resolve to install properly.

So I had assumed it was part of Windows. In fact, it's in my Win10, Intel, no AMD anywhere.
 
True. I should have been clearer. In my Win10 major removals preset, I had removed RemoteFX. And opencl.dll is still in place. (IOW, no need for me to protect it.)
 
You must log in or register to reply here.
Back
Top