Cumulative Update KB4497093 for Windows 10 Insider 1903 build 18362.86 Insider

Faith said:

I hope not! RE2 Remake is amazing and I'd hate to run into this error later this month. Do you have to run it though? It should already be installed with the game and operatingsystem. Try verifying the integrity of the game install cache by right clicking on the game's properties in Steam. When scouting around I can find users having black launch issues; Some got it resolved by reinstalling vc_redist.x64.exe 2017 specifically, you may try that if you haven't already. I can also see certain games having evr.dll errors on Windows 10 N Versions because of an outdated media feature pack, probably not related to your problem. Just stay on 1809 until 1903 is out in full glory. If it's a widespread issue it will certainly be resolved when there's more users reporting it, because right now not many users are on 1903.

The problem is not related to integrity or anything else on the game, checked it too, it just simply gives an directx error because it needs the DirectX libraries when you start it, same thing happens on 1809 but after installing the DirectX redist from steam it works fine or even installing the websetup for directx which i usually use every time i install a fresh OS. That installation doesnt work, it seems like when it tries to install any of the DirectX cab files it pops up an internal error and cant install the Libraries. As said, this libraries are necesary for many games, many old games but also some new games. Also i installed many vcredists versions (x86 and x64) because i thought too that this has something to do with it but it didnt solved it. I know that this is not a final release but as i didnt see nobody talking about this problem i thought that maybe asking here to be sure its not only on my side would be better.

Bree said:

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

Thank you very much

Bree said:

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.

Yes, you are right, im an insider since a lot of time but i have downloaded the .iso files just for fresh installations as while im testing i like to have it as clean as possible. Thats why i have 3 different build numbers for this new 1903 update but on all three i experience the same problem. I know its not the official final version and that it could still have bugs but the reason im not reporting it is that im not 100% sure if it only happens to me, thats why i reported my problem here to see if anyone else has tried to download the directx webinstaller or used any June 2010 dxsetup on this build to see if its installs without error. I always like to test the windows versions outside my main computer to be sure that everything is working and as i have now 2 weeks of hollidays im testing the new version build. But due to this problem i cant test many of my games (many of them are dependant on the directx June 2010 package). I only want to be 100% sure its not only on my side before reporting it, i think if this problem is confirmed it could be a really big issue. Only seen this problem some years ago and it was caused by Kaspersky antivirus so my first thought was maybe Windows Defender blocking it, but as said, i tried to turn it off temporary and it didnt helped, after that i completly disabled it (disabling first the anti tamper and then modify the group policies) but this also didnt helped.

Thanks to all for the replies, im now installing again a fresh copy into another computer (a laptop) to see if its maybe related to hardware (i dont think so, but hey, with trying it i dont lose nothing, only time hehe).

Regards and thanks again !!!

Bree said:

Me too, a non-Insider with an 18362.30 ISO from UUP Dump. Seems 18362.86 has successfully served its time in release preview and is now marked for general release.

Hi there

@Bree

Until the VMWare issue is fixed with this build it can't really be considered ready yet for general release -- loads of business as well as home users use VMWare and they can't easily switch to HYPER-V etc - especially at a business level - a switch of that type of process takes a long time to plan and implement properly in any decently sized business. Home users of course have different choices though - but again I'm sure they want their existing Software (especially paid versions) to work properly !!!!! before doing any general release Windows update.

Cheers
jimbo

I dont have any issues in vmware workstation, what cpu are you using, system specs, software environment, I would also reset to default all vmware internal settings. Are you using a custom ini file for your VM's to workaround issues?

Josey Wales said:

I was on The RP and when I installed ICUE 3.15.101 I was knocked out of it so I left it as . I know ICUE has something with notifications but everything works.

Icue is buggy as hell, I would uninstall it and use the latest release of corsair link

jimbo45 said:

Bree said:

Me too, a non-Insider with an 18362.30 ISO from UUP Dump. Seems 18362.86 has successfully served its time in release preview and is now marked for general release.

@Bree
Until the VMWare issue is fixed with this build it can't really be considered ready yet for general release...

1903 isn't on general release, you have to jump through hoops to get it if you are not an Insider. But once installed the CUs for 1903 are behaving as if 1903 is already on general release. They are delivered to non-Insider installs once they have been tested and approved in RP, just like recent CUs for 1809 have been tested in RP before being marked for general release.

Hi there @f14tomcat

The VMWare problem on 1903 release is nor running the release as a VM BUT when you use build 1903 as a HOST. When used as a HOST any VM will hang when you try and attach a n external USB to it.

With Build 20H1 as a HOST the VM will GSOD rather than hang when attaching a USB device.

On a Linux Host for example there's no problems running these builds as VM's --it's when you use them as a HOST that the problems occur.

Have you tried running this build as a HOST and then testing VMWare - don't forget to try and attach an external USB to the VM to complete te test.

Cheers
jimbo

f14tomcat said:

Thanks for the reply. So I am correct saying VMware runs fine under RP. That is my main concern right now, since 18362 RP is essentially the next public build. That's what I tested. Release Preview running VMWare 15.0.4, and the 3 OS's under it, 1809, 1903, and 20H1. All seemed to be running fine, and previously they would hang on Guest boot, requiring a 1903 reboot. I understand what you are saying about the USB attachment. I have no need for that, so have not tested it, nor am I concerned. Not to say it's not a problem, it is, just not to me at this time. I'm really most concerned VMWare behaves, for me, the way it is currently behaving under 1809.

As I stated in previous post, this appears to have just started working (my environment and needs), whereas a few days ago it was not. Only significant change was the 2 .net MS updates.

So, aside from any USB issue, is VMWare running normally on 1903, and when did it start running fine. Just trying to pinpoint what caused it to start working and when.

Thanks.

Hi there

f14tomcat

Thanks for the explanation.
I'm just testing 20H1 now the latest update 18894 released yesterday -- it runs fine as a VM and can attach devices - using HOST - Linux Centos 7.6

Will try it as a HOST on a spare laptop

I do need the attach USB devices to work as I use laptop when travelling to stream media from a Linux VM with a passport type 4TB USB disk attached. I have the files on a Linux VM because I use a native NAS system for streaming when I'm at home and Windows still has that problem with long file names etc -- once you have devices of several TB the file length restriction becomes a pain !!!!

Cheers
jimbo