Cumulative Update KB4497093 for Windows 10 Insider 1903 build 18362.86 Insider

erpster4 said:

I'm downloading 18362.86 from a UUP dump instead of 18362.30..

I redid my download from UUP dump and with the guidance of Keri's video tutorial extracted etc to produce the iso for 18362.86. I copied the iso into my laptop's hard drive rather than use the external drive that typically would be used. BUT after a long session of install, checking for updates, doing updates when 1903 was in place it was at .30 instead of .86 and there are no updates via the settings/update.
Oh well, all the parts and pieces appear to be in order and it all seems the same. Even the networking to the desktop stayed in operation. Now my curiousity is appeased. LOL!
Rose

I have this build on 3 desktops and 2 laptops and have had no problems with it.

I have a laptop with a dGPU. Will there be problems if the dGPU is recognized as GPU 0 (and iGPU as GPU 1) in Task Manager on a fresh install?

Now I am at .86 via WU this wkend. I had a look in WU on Sat and the .53 was there. Then Sun 5th May .86 was available. So the ABOUT info has 1903 18362.86 but the same KB4497093 is listed in WU for download and it is already installed. I put the updates on pause. I don't want to go on into the next versions and I'm not an insider. I just wanted to see if I could do this routine with uup dump on an extra computer. There were no glitches for me and none of my settings were affected.

Hopefully the 1903 official update will be available sooner than later this month.

With build 18362.1 there were no errors making a backup using the backup app in Control Panel, after updating to 18362.86, the following error will appear each time I run the backup

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary WinQuic.

System Error:
The resource loader failed to find MUI file.

I cannot find anything online about this specific error, any ideas

Hi, first i want to say that my english isnt good at all. I have tried out the new update 1903 on a fresh install on a new computer and everything seems to work fine but there is an issue i cant fix. I was testing some games on the latest build and for some games on my steam library like Resident Evil 2 Remake, there is a need to install the DirectX libraries with the DXSetup.exe that comes with the game. The problem is that when i try to use the installer or even download the latest runtime (webdxsetup) i get an internal error every time i try to install it, no matter which directx installer i use (tried installers from many games and also downloaded installers from microsoft). I reinstalled net frameworks, even removed the directx registry entry, turned off windows defender in soft and hard way and many more things, no matter what i do, its impossible to install. So i just plugged in another ssd to make a fresh install of 1803 and directly installed directx without problems, formated that ssd again and installed 1809 and it was working too, last test was to install 1903 again and install directly directx but again, same error. So, im pretty sure there is something wrong with this, the build number is 18362.86 but also tested on 18.362.53 and problem is still there.

Has someone else the same problem? Its really strange that nobody here or at microsoft has the same problem. As said, this only happens with some games were you cant run the game without installing the DirectX redists. Also apart from that, the update looks very stable, hope that this issue is not on the final release.

Regards !!!

K4miKaZe said:

Hi, first i want to say that my english isnt good at all....

Welcome to TenForums K4miKaZe. If you hadn't said, I wouldn't have known. Your written English is fine....

I have tried out the new update 1903 on a fresh install on a new computer and everything seems to work fine but there is an issue i cant fix.. last test was to install 1903 again and install directly directx but again, same error. So, im pretty sure there is something wrong with this, the build number is 18362.86 but also tested on 18.362.53 and problem is still there.

If you are running 1903 you are either an Insider or (like me) have downloaded an ISO (from UUP Dump?) to install it. 1903 is currently in the Insider Release Preview Ring to detect problems like this before going on general release. After the problems with the 1809 launch Microsoft should be listening particularly carefully to feedback this time round. Insider or not, you should report your problems in the Feedback Hub.