Or number 935. Download them from Microsoft update catalog and install them manually by clicking on downloaded files.
is there any way to be able to add the "nointegritychecks" value when booting from an install.wim? (i mean to add the value "nointegritychecks" in the install.wim and thus be enabled when the system is installed.)
After applying WU_Fix_For_Vista_WS2008.txt MSE stops finding antivirus database updates. what can I do to make MSE able to detect and download antivirus databases again?
just download the first ms security essantial from WU and it will search for update just dont update to latest version (reply for xmr2)
Just a bit of extra info, but since I switched to using the Legacy Update server, I haven't had to use the WU_Datastore_Fix. I've done multiple clean installs and never had an issue installing all updates (except for the latest .NET Framework, but that's a separate issue). Not sure why changing to the Legacy Update servers has fixed the issue for me, but it's no longer needed from my experience. Any occasional error code I have had lately has been fixed with a simple reboot. What about others? Has anyone else tried it without the WU_Datastore_Fix lately?
Burdus77: What I stated in posts #929 and #932 is as far as I've gone, and my testing laptop is currently sitting idle. I'm waiting for June 11th patch Tuesday to see what happens with Windows Update.
Thanks Captain, I must have missed that about the WU_Datastore fix. Good to know. I have no idea why changing servers fixes that issue, but hey, if it works it works!
Hello! I basically never used the datastore fix in my script (it is there but it is commented out since forever). What I found out is that the datastore fix is needed only if kb4575904 is installed. So since kb4575904 is replaced by kb5016891 (the newer ESU LPP) I just skip the old one and voila. The datastore is not needed (this might change in the future though as we get more and more updates). The only benefit that you get by installing both updates is that you won't get offered the 2020-01 SMQR which is just a metadata thing. All that applied to offcial WU before April since I didn't have the time to figure out how to make legacy update to work.
Captain, how were you able to install the .NET updates without the bypass installed? Even when I try to maually install them the .NET 3.5 SP1 and .NET 4.6.2 updates fail for me without the Bypass installed.
Thanks xrononautis, I have only ever installed the latest ESU Licence prep update so that's probably why I'm not having to install the Datastore fix. And yes I do get the 2020-01 SMQR showing up every time, which is a minor annoyance!
When the KB5038291 NET Framework 4.6.2 update failed to install, I deployed BypassESU-v7-WS2008 and did a restart, but that did not help. I then manually installed the KB5037917 NET Framework 4.6.2 update. I did not install the NET Framework 3.5.1 update.
If I don't have the Bypass installed KB5037917 won't manually install for me, neither will the 3.5 SP1 Update. I think the Bypass should still be included in your instructions, as I see it's been removed. The Latest .NET updates won't install through WU anyway, so only manual installation can happen. Without the Bypass though they won't install manually (at least not for me they won't, and I've tried multiple fresh VM installs).
This is what I get without the Bypass installed: And with the Bypass installed: The .NET 2.0-3.0 Update doesn't seem to be affected without the Bypass.
I don't do virtual machine installs. I do normal installs. I don't know if the difference between both types of installs causes different problems. I'm going to wait until June 2024 patch Tuesday to see if there's still an issue with installing a NET Framework 4.6.2 update. It takes several hours, so I have no plans to test the guide again from beginning to end anytime soon.
Why don't you use the repacks that abbodi makes? Much cleaner and easier solution if you ask me. And yeah the bypass is not needed for .net 2.0 .net3.0 .net3.5 as those are normal msu files.