Windows 10: 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

:)

 

Homegroup

If I click on the "homegroup" tab in Windows explorer it prompts me for the homegroup password but rejects it as incorrect.

If I click on the other laptop name (running the anniversary update) in Windows explorer, it prompts me for

network credentials but does not accept the microsoft login, which was what worked after the original Windows 10 upgrade.

 

Error 0x80070057

Try Step 4

FIX: Windows 10 Anniversary Update: Error 0x80070057

https://windowsinstructed.com/fix-windows-anniversary-update-error-0x80070057/

 

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.

 

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

 

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"[/quote]

 

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

 

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.

 

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.

 

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

 

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.