Windows 10: Verifying shim SBAT data failed:

Trying to boot from a usb stick In win 10 I get the message "Verifying shim SBAT data failed: Security Policy ViolationSomething has gone seriously wrong: SBAT self-check failed: Security Policy Violation" Can someone help me resolve it? Is this from the latest windows update?This seems to have started right after a win update but I'm not sure if it's a coincident or not. Thanks for any help

:)

 

EmulateHeap compatibility shim broken on Windows 11 22H2

This is a BUG REPORT.

The EmulateHeap compatibility shim has been broken on Windows 11 22H2. It had worked fine in Windows 11 21H2, and also works well on Windows 10 22H2.

To enable the shim:

1. You can utilise Microsoft Application Compatibility Toolkit.
   
2. As this shim is a part of the Windows 95 and Windows 98/ME application compatibility modes, they can be directly enabled by changing the combability mode setting of an application, i.e., can be activated directly by right-clicking on an executable file -> Properties -> Compatibility -> Compatibility Mode - Windows 95 or Windows 98/ME.
   

When active, most of the programs become problematic. Some famous applications having issues after enabling shim by any of the either method are described below:

1. Grand Theft Auto Vice City - game loses sound
   
2. Grand Theft Auto III - game loses sound
   
3. Grand Theft Auto San Andreas - CRASH
   
4. Need for Speed Most Wanted 2005 - crash
   
5. Thief II - game hangs
   
6. Thief 1 Gold Edition - game hangs
   
7. Any InstallShield program that wants Windows 9x check - CRASH
   

I have tried the usual "System Integrity Check" and "Reset Windows" ideas earlier, none of them work.

Almost all applications requiring the shim no longer work! Please look into this issue. The issue has been raised earlier in other tech forums and no one has been able to solve it yet.

Thank you.

 

Lost data from hard drive, what to do now?

Well, I'm sorry to hear that it's a WD My Passport that failed on you, @tomhenry ! *Frown
I'd recommend you to try using a different USB cable with it and see if that will help your system to detect it without it disconnecting.
I'd also suggest you to go to Disk Management and see how the drive is listed there. It won't hurt to check up on the health and SMART status of the HDD by running the QUICK and EXTENDED tests from the WD's Data LifeGuard Diagnostics. Here's a link to the available software: http://products.wdc.com/support/kb.ashx?id=11ZOpD

Give these troubleshooting steps a try and keep us posted with the results!
SuperSoph_WD

 

BSOD hidclass.syss with verifier enabled

Hi DocSams,

Could you upload the memory dump, C:\Windows\MEMORY.dmp, to onedrive and post a share link. The minidumps provided severely lack in data.

If you haven't yet, please disable driver verifier.
Resetting driver verifier options (recommended in this order)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. On 3 boot failures, you'll boot automatically to the recovery options,
   • click Troubleshoot
   • go to the advanced options
   • choose command prompt
   • enter the below command
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code: