Search results

1) That's correct, based off of everything I've read, but not personal experience. They are .msu files and not msi files though. You just drag it into the updates area - nothing special. But you do have to integrate it into both the Windows version that you want (Pro, for example), and also the...

Like I said before, "Access denied" is obviously a permission issue. Did you Make sure that's all good? Maybe you should remove all permissions from those files and just add a single one for Everyone to have full control over them. And although I believe it's a permissions issue, if you want to...

That's the SHA-256 hash... It's right.

I am able to integrate both KB2990941-v3 and KB3087873-v2 without any issue into both boot.wim and install.wim using NTLite, tested on both an untouched ISO from Microsoft, as well as one that I've already integrated a bunch of updates into. Maybe you should double check your files and their...

Well, as I said, I didn't actually do this since I went the Samsung route, so I can't tell you that it definitely works from personal experience. But straight from Microsoft themselves, for KB2990941: And the guide I linked to was pretty clear as well. So yeah, integrating KB2990941 into...

I feel you. I hate Windows 10 I have a Samsung NVMe drive, and they provide their own drivers, so I didn't need this. However, there are hotfixes available that Microsoft has already removed the link(s) to. I downloaded KB2990941-v3 from them when they still had it on their site but there are...

Beautiful. It did not re-offer and re-download the latest cumulative update. Thanks, and thanks to abbodi86 for the insight. Edit: Was offered the cumulative update again after Windows installed some language related thing. Trying to figure out how to stop this now. I checked before and after...

Unfortunately, this isn't the problem. I just redownloaded all of the MSU files from Microsoft Update Catalog and checked the hash against the ones I had and they all match. I do feel like I've had 1 instance where Windows update didn't try to redownload the latest cumulative update, but I don't...

I know you've already solved this, but the solution I've used in the past was to run "sources\setupprep.exe" instead of "setup.exe".

edge914, I'm not sure how the threads you linked to have anything to do with what the OP is asking. He doesn't seem to be saying that things he removed are brought back by installing a Windows Update. I have noticed the same thing that the OP has for some times now and would like to know if...

The source are the commands in the opening post. You can extract it out of the exe to see it. For me, this has worked when integrated with NTLite in post setup for the December 2019 and January 2020 updates + the wallpaper fix (KB4539602) that was released in February 2020.

sli, I already gave the commands to run to get rid of EOSNotify in the opening post. It works for every update that adds the files / enables it, including the latest wallpaper fix update for those without ESU. I'll attach something that you can throw into the post setup section in NTLite. The...

I tried testing out the removal of EOSNotify in NTLite and it definitely stopped the notification from running, but the files still seem to be there. I went into Settings and disabled it first, and then I went into Components and removed it. If I reload the image back into NTLite, I still see it...

Add an option to remove EOSNotify which is included in the December 2019 and January 2020 cumulative updates for Windows 7. I run this in post setup with PowerRun to get rid of all traces I could find of it: schtasks /delete /tn "\Microsoft\Windows\Setup\EOSNotify" /f schtasks /delete /tn...

This is not true

It's not so much a problem for me because I didn't use that setting, but I did test it out for you and yes, it's still broken.

I just created an Windows 10 1909 install with this setting set to disabled as well, and it in still not working as of version NTLite version 1.8.0.7261

So for the October 2019 roll up (KB4524157), Microsoft wants you to install KB4474419 before installing the roll up.... but the October roll up replaces KB4474419... Edit: I created an install with the October patch but without KB4474419. Windows updates wants to install KB4474419 in that...

Can drivers integrated through NTLite be removed from Windows that has already been installed using the installer that had the drivers integrated? For instance, will DDU be able to uninstall any NTLite-integrated video card drivers?

In case if anyone is wondering, it is definitely Microsoft's error.