Unlucky Me ! !

1 Like

DANTE hmm this didn’t show up or notify me before. Anyway check the BIOS version, if it doesn’t have 4601 from 05/22/2014 download and install it from here. Asua P8H61-m_LX

Also these
Management Engine Interface V11.0.0.1157 for Windows 10 32bit & 64bit—(WHQL).

Realtek Audio Win10 32bit&64bit V6.0.1.7503-WHQL

Realtek LAN WIN10 32bit&64bit V10.1.505.2015.

1 Like

Spinalfailed kk let me check

Mark2K77

there you go

1 Like

1 Like

Moved to Tech Support. Good luck!

2 Likes

Mark2K77 still same

can you run this in command window?
dism /online /cleanup-image /restorehealth

1 Like

DANTE milkywayman cause of this error is most likely in safe mode, and in fact some of services are disabled in safe mode … so first thing on to do list is to open services.msc or elevated command prompt

And find Trusted Installer or Windows Modules Installer service and enable that service in services.

Or in elevated command prompt sc config trustedinstaller start=auto if command is completed successfully CMD will return this “[SC] ChangeServiceConfig SUCCESS"

After that sfc /scannow command will work

If we will run random commands we will end up in bigger chaos … it is always cause of the problem and the consequences …

1 Like

Mark2K77 i have done this “Windows Modules Installer service and enable that service in services.” still same

it seems to me, that someone needs to remote connect to your pc to check things out, it should be a lot faster :slight_smile:

2 Likes

DANTE at this point I will agree with milkywayman best would be to remotely connect on your PC and check system …
Another option is that you back up data from your PC on external drive … Then first configure BIOS update BIOS if necessary, do low level formatting of HDD … And proceed with clean Windows Installation (basic system drivers + diagnostics tools)… after that test system … then we will maybe know what is the cause of problem …
Let me know on which way you wish to move along … so remote connection and diagnostic or clean system setup then diagnostic?

1 Like

Did you try running the cmd.exe as admin before running the sfc /scannow?

Mark2K77 According to an earlier post it has a BIOS from 2010 and the most recent is 2014. I would start with that. Then troubleshoot every other issue! But that’s me and my PC’s are working great! haha

1 Like

Gorkie yap

Mark2K77 i will let you know

sorry for late reply i wasnt sober enough last two days :stuck_out_tongue:

and i think remote connection and diagnostic is best choice for me

1 Like