PDA

View Full Version : Getting a weird shell32 error in windows 10 fcu



Nimbi
November 11th, 2017, 07:30 AM
Hello,


I'm getting this weird error in Windows 10 FCU that seems to be pointing towards an error with shell32 and was wondering if anyone knew what was causing it. Here's a screenshot:


78978


I first noticed this when I tried to load a start button into StartIsBack++. At the time I thought StartIsBack++ had gained a new glitch. But then it happened again when I tried to load a plugin into AIMP.... So now I'm starting to wonder what's really causing it. Anyone here recognize this? If so, do you know a simple way to fix it without having to run a reset or without having to run sfc /SCANNOW?


---EDIT---

Just ran sfc /VERIFYFILE=c:\windows\system32\shell32.dll and it couldn't find any errors with shell32.dll .... so not sure what's going on with that error.

Nimbi
November 17th, 2017, 11:13 PM
I found the cause of the Shell32 error. It's the explorerframe.dll made by gsw953 of which I obtained from http://www.msfn.org/board/topic/170375-oldnewexplorer-118/?page=54

https://i.imgur.com/PsJGDR2.png

For some reason that explorerframe.dll breaks Shell32

This error starts showing up every time I apply that explorerframe.dll

Mr GRiM
November 17th, 2017, 11:15 PM
I found the cause of the Shell32 error. It's the explorerframe.dll made by gsw953 of which I obtained from http://www.msfn.org/board/topic/170375-oldnewexplorer-118/?page=54

https://i.imgur.com/PsJGDR2.png

For some reason that explorerframe.dll breaks Shell32

This error starts showing up every time I apply that explorerframe.dll

I am using the exploreframe.dll as well and not getting any errors, just changed the start button to test if I could reproduce it.

Nimbi
November 17th, 2017, 11:19 PM
I am using the exploreframe.dll as well and not getting any errors, just changed the start button to test if I could reproduce it.

Strange, for me the explorerframe.dll is causing those errors... Maybe it's because I'm on a CyberPowerPC? Perhaps CyberPowerPC has some sort of lockdown built into it? I know it locks down recovery media to the recovery disc to the point where I can't even make recovery media with it, so it wouldn't surprise me if there were other lockdowns...