Known and Resolved issues for Windows 10 May 2020 Update version 2004

Page 9 of 62 FirstFirst ... 78910111959 ... LastLast
  1. jimbo45's Avatar
    Posts : 9,277
    Windows / Linux : Arch Linux
       #80

    PurSpyk said:
    Those aren't even all the issues. Odd how they can release a version with so many issues, with so many people forced to work remotely.
    Hi there
    I doubt if people would mess around with their work computers (or machines they use for work) while working remotely -- especially if they need those machines for work so they can get paid.

    If people are imbecellic enough to insttall untested builds on their machines while working remotely where any sort of complex I.T support could be tricky then IMO they deserve everything they get !!!

    However I agree it should not be acceptable for Ms to release potential RP / R.T.M builds full of defects.

    That said I don't have too many problems with this version but I wouldn't use it on an I.T contract for remote clients !!!!

    Cheers
    jimbo
      My Computer


  2. Posts : 1,133
    Windows 7 Home Premium x64
       #81

    Microsoft's own Surface / Surface Pro devices are not even getting the May 2020 Update yet due to some compatibility issues.

    A comment from Mr. Thurrott himself on his web site:
    Windows 10 Version 2004 is Now Available - Thurrott.com

    Surface Pro 7 has a compatibility blocker.
      My Computers

  3. sygnus21's Avatar
    Posts : 4,303
    Win 10 Pro (x64) 1909 18363.836
       #82

    erpster4 said:
    Microsoft's own Surface / Surface Pro devices are not even getting the May 2020 Update yet due to some compatibility issues.

    A comment from Mr. Thurrott himself on his web site:
    Windows 10 Version 2004 is Now Available - Thurrott.com
    I missed where Thurrott stated in the article the Surface / Surface Pro devices aren't getting the update. I see someone from the paul-thurrott "staff" posted the "Surface Pro 7 has a compatibility blocker".
      My Computers

  4. Brink's Avatar
    Posts : 49,780
    64-bit Windows 10 Pro for Workstations build 20161
    Thread Starter
       #83
      My Computers

  5. eLPuSHeR's Avatar
    Posts : 2,234
    Windows 10 Home x64
       #84

    Hi.

    I have manually updated three PCs with no big issues so far. What I have noticed is that now there is a non-deletable file (DumpStack.log.tmp) at the root folder of C drive. I don't know what is for.
      My Computer

  6. CountMike's Avatar
    Posts : 17,029
    W10 Insider + Linux
       #85

    eLPuSHeR said:
    Hi.

    I have manually updated three PCs with no big issues so far. What I have noticed is that now there is a non-deletable file (DumpStack.log.tmp) at the root folder of C drive. I don't know what is for.
    Known and Resolved issues for Windows 10 May 2020 Update version 2004-image.png
      My Computers

  7. sygnus21's Avatar
    Posts : 4,303
    Win 10 Pro (x64) 1909 18363.836
       #86

    How big is the DumpStack file?
      My Computers

  8. Brink's Avatar
    Posts : 49,780
    64-bit Windows 10 Pro for Workstations build 20161
    Thread Starter
       #87

    UPDATE 5/28:

    New known issues added for Windows 10 version 2004. Please see first post for more details.
      My Computers

  9. ignatzatsonic's Avatar
    Posts : 1,509
    Windows 10 Home, 64-bit
       #88

    I just tried to use mp3gain for the first time after updating.

    It won't run at all from it's standard taskbar icon. I get this error, which is difficult to cancel or get around. I had to force a restart.

    I can't find the referred to .msi file anywhere.

    I uninstalled mp3gain and tried a reinstall and was faced with the same error message.

    Any ideas---or possibly a replacement for mp3gain if necessary.

    Known and Resolved issues for Windows 10 May 2020 Update version 2004-mp3gain-error.jpg
      My Computer

  10. AndreyT's Avatar
    Posts : 406
    Windows 10 Pro
       #89

    I just tried to force-install the 2004 update by running the Update Assistant.

    The update process started normally but failed (and reverted) somewhere at final stages, most likely - after the final reboot. The initial blue-screen error was PAGE_FAULT_IN_NONPAGED_AREA for aksfridge.sys module. This module is a part of HASP software licensing service. I don't know what installed it on my machine and I see no way to uninstall it at the moment. I had to edit the registry at HKLM\SYSTEM\CurrentControlSet\Services\aksfridge and set Start = 4.

    After that I had subsequent reboot failures of the same nature in aksdf.sys and hardlock.sys - all apparently components of the same HASP package. Fortunately, disabling these three services (through Start = 4 in the registry) proved to be sufficient to successfully install 2004 update.

    P.S. I wonder if anyone knows how to uninstall these HASP services entirely from the machine.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:24.
Find Us




Windows 10 Forums