Windows 10: why do Microsoft force there security sys and other product sys in win 10,11 that some...

Hate Microsoft force there security sys and other product sys in win 10,11 that some consumers don't wanthate edge, MS defender, MS antivirus MS hello pin MS Bit locker driver, phone link , MS not able to choose what updates to install or not install or able to uninstall products that don't want! hate MS using tacking cookies!

:)

 

Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics)

Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics). Is there any updated STTub30.sys which supports Windows 11 OS?

 

Steelseries Merc Keyboard driver alpham164.sys disabled after windows 10 creator update why? how to undo/force it?

well I'll do the best I can to go step by step:

• Boot With Driver Signing disabled
• With Zengine installed, go to your "Saved Bettam folder"\Kernel2k\Bettam12.inf.
• Right click and select install.
• Go to your %SystemRoot%\System32\DriverStore\FileRepository\ and make sure the Bettam12_* folder is created... *being the alphanumeric hash that is generated when you install a driver.
• If this folder is created then go to regedit
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
  • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam164.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
  • Edit the Source entry to your %SystemRoot%\System32\DriverStore\FileRepository\ bettam12_*\Bettam264.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham164.sys
  • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam164.sys
• Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Alpham264.sys
  • Edit Source to your %SystemRoot%\System32\DriverStore\FileRepository\bettam12.inf_*\Bettam264.sys
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam164.sys
  • Verify it contains the same information
• Look for Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/Bettam264.sys
  • Verify it contains the same information
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB in a VID Key
• If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Alpham1
  • Change ImagePath to your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Bettam1
  • Verify it contains the same information
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in a VID Key
• If not Search for Alpham1 in that tree and change LowerFilters to Bettam1
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Alpham1
  • Change ImagePath to your your "Saved Bettam Drivers\Kernel2k\Bettam164.sys" folder
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Bettam1
  • Verify it contains the same information
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem34.inf
  • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\oem35.inf
  • Change both Default and Active to your "bettam12.inf_*" folder thats in System32
• Go to Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_*
  • Change InfName to Bettam12.inf
  • Change OEMPath to your "Saved Bettam Files\Kernel2k" folder
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\alpham12.inf_amd64_932fbe5113b0010d\Configurations in a HID_Keypad entry
• If not Search for Alpham1 in that key and change LowerFilters to Bettam1
• Look for Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*
  • Verify it has the same information as the previous Alpham1.inf_* entry
• Search for Bettam1, result should be Computer\HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\bettam12.inf_*\Configurations in a HID_Keypad entry
• If not search for Alpham1 and change LowerFilters to Bettam1

If any of the Alpham entries are missing, or you previously renamed any of the Alpham keys, reinstall Zenginge from scratch and then start from the beginning of these steps.

Reboot your computer with Driver Signing Disabled again and See if Zengine is working. If Zengine is red Open Device Manager. Verify the Bettam164.ys and Bettam264.sys are listed, If they are missing and if there is no Alpham164.sys or Alpham264.sys then
begin updating drivers. Use the saved Bettam drivers in your Kernel2k path. If everything is working you can reboot normally.

 

PxHLpa64.sys Incompatable with Win 11

I upgraded my HP Spectre laptop from Win 10 Pro to Win 11 Pro and everything worked perfectly except that Memory Integrity cannot be turned on due to a compatibility issue with PxHLpa64.sys. I've looked at the online solutions for removing this driver and have been unsuccessful at doing so. The last thing I tried was running Autoruns.exe as administrator; the driver was found, but I could not delete it.

I cannot find any device on my laptop that uses this driver. Is there a way to safely delete it?

Thanks, John