Windows 10: im looking to re enable sys main service

i cant find it in services.msc and i can find anything about it online can anyone help me?

:)

 

How to use Sys. Config. to get rid of un-needed sioftware

Hello,

Here's the steps I'm doing, cuz i believe they may stop/disable UN-wanted software.

I open up "System Configuration." & click on "Services." I see a very long list (counted @ 217 items). ALL have a check-mark. Some are "Running". Most are "stopped."

I put a check-mark in "Hide all Microsoft Services", and the display changes to 7 items (all with check-marks) and all are labeled "stopped."

"Enable all" is grayed out. I click-on "Disable all."

Each item's check-mark disappears. "Hide all Microsoft Services" is still checked.

I click "OK". The window closes on its own.



I want to check to see if Sys. Config. has
retained these commands to 'Disable" this mass of software.



It didn't. Sys Config looks exactly like it did when began the process.



I did a re-boot & nothing was retained of my changes in Sys. Config. It's as if I did nothing.

Please would someone send me the correct steps on this ?

Thanks,

Gary

 

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.

 

Help with the Windows Search Service failed

Hi,

Having some damaged system components is one of the possible causes why the services in the system are failing. For us to provide an accurate solution, we would need you to answer the following questions:

• Which build, version and edition of Windows is installed on your computer?
• What changes have you made to your computer before this issue occurred?
• What troubleshooting steps have you done so far?

In the meantime, we suggest refreshing the Windows Search service. To do so, follow these steps:

• Press the Windows key + R to pull-up the Run box.
• In the Run box, type services.msc and then hit the Enter key.
• In the Services window, look for Windows Search, right-click on it and then choose Stop.
• Restart your computer.
• Pull-up the Services window again.
• Look for Windows Search, right-click on it and then choose Start.

We are looking forward to your response.