windows 10 anniversary explorer error ???


  1. Posts : 1,104
    win 10 pro x64 os build 20H2
       #1

    windows 10 anniversary explorer error ???


    OMG since i got the update to anniversary i have this stupid error now every time i restart or log of my system why is it MS breaks things how do i fix this it was never there till this update. here is the stupid error.

    explorer.exe - Application Error
    Message The instruction at 0x00007FF7090290E2 referenced memory at 0x0000000000000030. The memory could not be written. Click on OK to terminate the program
      My Computer

  2. dalchina's Avatar
    Posts : 30,090
    Win 10 Pro (1903)
       #2

    Would be interested in the answer as I've often seen this pre and post AU upgrade.
    I've just never got round to investigating, I'm afraid, as it's not affecting things normally, but does delay shut down/restart.

    Have a look at your event log and see what you can find.

    Also try using Shellexview (free) to disable all non-MS context menu entries and see if that has any effect.
    (Run it, hide MS entries, disable all others, noting there's a 32 bit option too).
    No log off needed for it to take effect.
      My Computers

  3. CountMike's Avatar
    Posts : 18,374
    W10+Developer Insider + Linux
       #3

    Happens to me every time during restart after update/upgrade, doesn't show up at later restarts.
      My Computers

  4. Edwin's Avatar
    Posts : 17,152
    Windows 10
       #4

    Save the following to a text file with .reg extension and run it.
    Problem solved.

    Code:
    Windows Registry Editor Version 5.00
    
    
    [HKEY_CURRENT_USER\Control Panel\Desktop]
    "AutoEndTasks"="1"
    "HungAppTimeout"="1000"
    "WaitToKillAppTimeout"="2000"
    "LowLevelHooksTimeout"="1000"
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
    "WaitToKillServiceTimeout"="2000"
      My Computer

  5. CountMike's Avatar
    Posts : 18,374
    W10+Developer Insider + Linux
       #5

    That's not gonna stop it from happening, just auto close.
      My Computers


  6. Posts : 1,104
    win 10 pro x64 os build 20H2
    Thread Starter
       #6

    Wish i new what it was glad i'm not the only one who is having this i tell you MS needs to get there stuff together and not break things.
      My Computer

  7. CountMike's Avatar
    Posts : 18,374
    W10+Developer Insider + Linux
       #7

    Tonyb said:
    Wish i new what it was glad i'm not the only one who is having this i tell you MS needs to get there stuff together and not break things.
    It does reference some memory address problem, wander if it's because of memory compression, that's only thing that's radically new.
      My Computers


  8. Posts : 1,104
    win 10 pro x64 os build 20H2
    Thread Starter
       #8

    Maybe not quite sure i have searched the error on the internet nothing shows up for it, when you ask MS they just blame it on applications you have installed , like wow it was not there till you updated my pc.
      My Computer


  9. Posts : 2
    windows 10 professional
       #9

    I have the same exact error after the anniversary upgrade... is there a solution for it already? I didn't change anything and before the upgrade it never happened.
    Cheers
      My Computer

  10. dalchina's Avatar
    Posts : 30,090
    Win 10 Pro (1903)
       #10

    It sometimes happens, sometimes doesn't. That tells me it's not a shell extension, for example, else it would happen every time.

    I've not seen a solution for it yet, or really looked for one.
      My Computers


 

  Related Discussions
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 12:13.
Find Us




Windows 10 Forums