New
#40
Here is your confirmation:
Windows 10 May 2020 Update Breaks Intel Optane Memory - The Redmond Cloud
Here is your confirmation:
Windows 10 May 2020 Update Breaks Intel Optane Memory - The Redmond Cloud
Thanks IronZorg89!
I had an issue, the update completely wiped my system partition partition. The most recent change before that was iinstalling Gigabyte's RGB Fusion.
However it was my lucky day, I made a backward restore of my system from my backup Now I'm recovering everything from file to file from all my other drives.
If it was an issue with the update then beware otherwise NEVER use RGB Fusion from Gigabyte's website.
Last edited by Jerry06; 10 Jun 2020 at 14:37.
It’s not a recent issue, as the same error occurred on 1803/1809 and 1903/1909:
Intel® Optane™ Memory Pinning Error: ‘Unable to load DLL ‘iaStorAfsServiceApi.dll
I don’t know why Intel didn’t fix it about a year ago, as their changes caused it.
Intel's workaround was published months before the release of Version 2004:
How to Resolve Intel® Optane™ Memory Pinning Error: 'Unable to load DLL ‘iaStorAfsServiceApi.dll''
NMI, appeciate the link. Thank you! I am on 1909 and so far no errors. Then again I have only had the new laptop a few days.
Thanks for the added information, but I remember quite well having read about it in the past. It is like most of the tech giants are in a race condition with regard to fixing their issues. When one factors in the aftermath of COVID-19 like social distancing, telecommuting, etc... things are not getting easier. Case in point, look at all the issues known and unresolved we are having with Windows 10 May Update, despite all the time MS had to get this one ready.
Explorer got screwed up after this update. Every time I move or copy a bunch of files, windows complains there are already duplicates in the target path.
I think build 2004 is no better than build 1909 ... I notice some bottlenecks, but without showing excessive CPU or memory usage, kind of weird ... especially in full-screen games!The 1909 build for me was better at this point ... although there were also some problems!In general, archiving tasks are showing some greater impact, perhaps the bottleneck here is more evident.For the rest, for now, it's working.The last CU KB4557957 was installed without error and in a timely manner <5 minutes using the .msu file