Search results

Can they be set to be the same? If so, the NTLite should reject that with a message.

It depends on whether the changes you made in a previous iteration can affect the changes that you're making in the current. But it's not inherently crazy. For example, I start by taking an untouched iso and slipstreaming updates into it. Then I save it and make a copy of it. Then I work on...

Also, I just now checked the option link for the download, the MS Update Catalog for this KB . It shows a date of 2/25/20 for the 1903 & 1909 flavors. So I assumed - apparently incorrectly - that NTLite would reflect this date in its Updater list.

Thanks for checking. Perhaps MS isn't updating its file dates then. Update .mum. Hmm... I hope that opens with Notepad.

Just for grins, I looked up KB4497165 to see if my lowly i3-8100 is affected. (It is.) But my point in posting here is that MS says that the code/KB was updated on Feb 25 2020. However, NTLite 7330 is showing a build date of 1/21/20. (KB version 10.0.4.1.)

My first guess is that you have "Synchronize Time" set. But that's so obvious that I'm sure you know about that and it must be something else.

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.)

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.

In my obsessiveness I just couldn't resist one more experiment with Remove Reinstalls. The result surprised me. Here's what I did: Had been running Win10 1903 with three previous KB's. (A Service Stack (now obsolete I think) and two others.) I did a "clean" Refresh to 1909. That is, I did not...

Or, another way of asking this is, what's the difference between doing a Clean up from within NTLite and Remove Reinstalls? It seems to me that once you've done a Clean up, there shouldn't be any Reinstalls to uninstall.

I tried it. It doesn't work. But perhaps nuhi can make the settings.xml so it does work with this trick? (It's not intuitive. But is better than nothing.)

Any more news on whether Cortana can been removed from 1909 using later versions of NTLite and keep the search bar working?

Cool. That's for locking components. I wonder if I can copy the <CompoentFeatures> to settings.xml to lock them in? (I'll try it.)

I restored my previous Win10 1903 and did a new Refresh to a vanilla 1909 which only had 2 KB's slipstreamed into it. I have now run NTLite Live about 5 times on it as I carefully removed components from the mostly vanilla 1909. The last run was Complete Cleanup, which, surprisingly, found...

I think I've asked for this feature before. If not, asking again. I find myself using NTLite Live all the time on my Win10 box. Every time I start it, the Compatibility settings seem to default to a default. (I think.) And I keep forgetting to change it, since it's kind of "out of sight, out...

I did a Host Refresh from Win10 1903 to 1909 with a no-preset 1909. (Just 2 KB's.) So that puts a mostly vanilla 1909 in place. (Although, thankfully, most Settings seem to persist through the refresh.) Then I used NTLite Live to first remove Fonts, Languages and Keyboards. When I rebooted and...

Okay, I remember now. The log was in the NTLite temp folder. Now, if I am understanding this Feature correctly, if I were to Refresh Win10, and not use a Preset to remove anything from the fresh, new .wim, then in theory, Remove Reinstalls wouldn't remove anything. Is this correct? That is...

So, I did my first ever Host Refresh for Win10 using the NTLite Wizard. I went from 1903 Home to 1909 Home. I did a Trim first, which removed the only 3 KB's I had used for 1903. (None of which were a Cumulative Updates.) Then I had NTLite check for updates for 1909. It found a Cumulative...

Yep, as nuhi said in his July 26, 2019 post, switching disks. I just upgraded the OS drive on my Win10 box from a spinning HD to an SSD. Now I have to reactivate NTLite.

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...