Hello. I've created updated ISO of LTSC IoT 2021 (19044.3930) However, I cannot disable Microsoft Defender frop Group Policy (via enabling Turn off Windows Defender Antivirus), even though I previously disabled Tamper Protection. The only way to disable Windows Defender is by bruteforcing services from Safe-Mode to disable startup. Why? I remember in previous versions, I was able to disable it only via gpedit.msc
Hello. It is possible to make a "Win 7" -> "Win 10 Ent. LTSC" upgrade ? Or does it need to be a fresh install. (I know this is not ideal)
I will be creating 2021 LTSC ISO, should I use ResetBase ON or OFF? Want to build a clean ISO for laptop
It doesn't do anything special, it only really deletes the superseeded components after integrating updates and thereby it decreases the install.wim/ISO filesize, so if you don't need the smaller ISO then you don't need to use it, but it doesn't really hurt either, only for 2019 LTSC is is not recommended to use.
I played with resetbase for years and in my experience, it only causes problems. It makes it impossible to install future cumulative updates. There's also the matter of the hidden registry key that makes it so that resetbase does what it's supposed to do, rather than just removing previous cumulative updates. Regardless of whether you use the hidden registry key or not, it causes the cumulative update install failure issue. I would just avoid using resetbase altogether. At least that way you could uninstall a previous cumulative update if it somehow was causing a problem with update installs. edit: I don't bother with updates anymore but when I did, I just ran "cleanmgr.exe" as admin and that would automatically remove superceded updates. So the functionality of cleaning up old updates without the bugginess of resetbase. Also, to build an iso with just the updates you need, you install iso in VM. Check windows update on vm. download the update files on the internet. Use W10UI to integrate them. Check result iso reinstall on vm to make sure it is correct and more updates aren't needed. When it is correct, you have an iso with all the files you need.
@murphy78 it only causes problems with IP level updates/builds. And with 1809 "reset pc" function. ps, the question was about W10UI function resetbase.
Hello everyone, well I finally decided to migrate to Windows 10 Enterprise LTSC 2021 x64, the installation went without any problems and I was very happy with its performance; as I always do a check-up on the system and check if everything is ok, when checking the system configuration I discovered that there was a problem that I have not been able to solve until now because this configuration appears as selective initialization and so I have already tried everything, but I didn't solve it; So I ask my dear companions who of course have much more knowledge than I ask for your collaboration, thank you very much
Oh it caused the same problems for me with w10ui using resetbase. It's not the script. It's the feature. Resetbase doesn't play nice with future updates.
Obviously you must resetbase. Especially making a fresh ISO (which is a waste of time for 99% of users, but that's a different story). What's supposed to be the point of not doing that? Wasting 2/3/4 GB of storage, depending the build, with no advantage in return?
When the system has to deal with tens of thousands of folders and hundreds of thousands of files (let alone the registry entries), the chances that something goes wrong are around the corner. But that's valid both for the reset base and the cumulative updates. And obviously the chances that something goes wrong are higher in W8.1/2012R2 that has hundreds of non cumulative updates and W10 14393 that has almost 6GB of data to replace. If something goes wrong, usually, a quick look to CBSlog is enough to fix any minor (but blocking) error, if that's not enough in place upgrades are there for a reason.
I used to resetbase with W10UI for offline integration in '22 and '23 resulting in errors months later when trying to update online. IT took me 3 rebuilds to figure it out that resetbase offline image was causing problems later on live system.
I never had once a problem resetbasing an offline image (and now it's a decade I play with it), usually the problems (if any) comes in live OS, because a minor ntfs error amplified by the huge amount of written files, because a running app interfered or alike. That said IT is plenty of exceptions and corner cases, but that's applicable to everything not just to DISM
It's been at least a year or two since I was doing the resetbase and fails but I seem to remember some generic windows update fail code. I looked it up on the internet and it was unhelpful. The only thing that fixed the issue was stopping the use of resetbase.