- #Use ntlite to strip down windows 7 install#
- #Use ntlite to strip down windows 7 windows 10#
- #Use ntlite to strip down windows 7 software#
This alone is a big enough reason to move on from an older Windows 10, such as 1809, 1903, or any other outdated edition.
#Use ntlite to strip down windows 7 software#
Anti-cheat software is now dropping support for versions of Windows that are no longer supported by Microsoft.
#Use ntlite to strip down windows 7 install#
I tried that Host Refresh option (that I still don't understand what it does) like someone recommended and it didn't work (as well as manually running the setup.exe from an edited 1809 ISO created by NTLite, ISO which I used in a VM before trying this and had some problems but I didn't care when I tried it in the host) but that might have happened because I used an edited 1809 ISO (created by NTLite, ISO which I also used in a VM before trying this and also had some problems but I didn't care when I tried it in the host) while having the 1803 version currently installed (an edited 1803 ISO created by NTLite was used).ĮDIT: This time I didn't uncheck the Windows Update compatibility and I still couldn't install the latest CU.ĮDIT 2: So, this time I used the 5_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_PT-PT image and now I have the 0x800f0982 error when I had the 0x80070032 error before so each time I have a different error.If you are a gamer then the first thing you need to know is that Microsoft seems to have gotten a lot of other companies onboard with their end of life road map. Another reason to not have done it already is that I'm having problems in a VM install (I always test the installs in VMs in order to know if I have any major problems before trying in the host) after removing and configuring things in the 1809 version like the problem about Windows Update (can't install the latest CU also) I mentioned before.
#Use ntlite to strip down windows 7 windows 10#
I still have the 圆4 1803 version (17134.254) installed in the host and I can't install the latest CU (because of another Windows Update error) like in the 圆4 1809 version I tested in a VM like I said before and I don't want to do a clean install because I'd have to copy all documents, install all program and configure settings again, although I'll have to do it later whether I like it or not, unfortunately (it looks like I'll have to do it every time a new Windows 10 version is released and after using NTLite because it'll have new functions/apps which I don't want and if I manually run the setup.exe of the new version I may have problems or still have those unwanted functions or some of them). Before that I had the 0x80070032 error (and even before that I had the 0x800f081f error although in this case I didn't use the preset I used when I had the 0x80070032 error and vice-versa) like I said in the first post and now I have the 0x800f0982 error like some users do/did and like I said before. I unchecked the Windows Update compatibility but does that mean that if I enable it in the hope of being able to install the latest CU I won't be able to remove some things I may have removed related with Windows Update after unchecking its compatibility (I think I don't removed any)? If I can install the latest CU after unchecking the Windows Update compatibility does that mean that I waited for a new NTLite version for nothing since I could have successfully install the latest CU in the 圆4 1803 (or even 圆4 1809) version with the latest NTLite versions at the time if I didn't uncheck the Windows Update compatibility (I doubt it since other users had and have this problem and I suppose all of them didn't uncheck the Windows Update compatibility)? I used the same preset like before but now I have a different error. I installed it in a VM through a clean install (like I always do). I am going to chalk this one up to something being different/wrong/changed in the new ISO and go with the original for now. Something feels wrong with it as it does not contain Windows 10 ENT N anymore where the original Oct 2 iso does. I suspect there is something very strange with the "new" LTSC iso issued this week. Everything installed great and I am now current at OS Build 17763.134. I did apply my usual NT preset to the image and installed to a VM using MDT 8450 with Windows updates coming via WSUS. UPDATE: I reverted back to the original LTSC iso - (Oct 2, 2018) and all updates install perfectly. I am going to try and install this clean via MDT with NO NTLite access and see if it's the image or NTLite.
134 CU simply dies with Error 0x800f0986 - which I believe indicates a corrupt image. The image arrives as OS Build 17763.107 but after added the latest service stack update - I am able to apply the Adobe Flash updates but the. Seeing this here as well - with the newly issued "Win 10 LTSC 2019" image just released this week.
0 kommentar(er)
