Unable to install *any* new device drivers or update existing ones

[britechguy]

In my opinion and experience, this really is a situation where first Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file, is absolutely easier than going through many diagnostic steps that may, or may not, fix the issue.

It is amazing just how many things a Repair Install will fix, all in one fell swoop, and the issue that had existed with being able to do one with the 20H2 Version has been fixed.

If that doesn't work, then either continuing down the path you're currently on or (after having made a system image backup, and separate user data backup for all accounts) Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Fetch the Win10 ISO File (since you'll already have the ISO file from having tried the repair install) is often the simplest fix.

Yes, it does mean you'll have to reinstall your software and, perhaps, some drivers, but at least you know you have a clean and fully functioning Windows 10 instance on which you're building. Right now, you don't, and likely won't, either.

 

[xevious]

Let's remove easyanticheat (if you are not using it).

From a command prompt (admin):

sc del easyanticheat

What audio device are you using (given that it says there are problems with it)?

I am unable to install any audio drivers which is part of the problem, neither the Nvidia high definition audio built into the GPU nor the Intel HD audio built into the CPU.

sc del easyanticheat (I have no idea what this is but suspect it came with some video game install). This gives "ERROR: unrecognized command" when ran from an elevated cmd prompt window.

 

[xevious]

In my opinion and experience, this really is a situation where first Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file, is absolutely easier than going through many diagnostic steps that may, or may not, fix the issue.

It is amazing just how many things a Repair Install will fix, all in one fell swoop, and the issue that had existed with being able to do one with the 20H2 Version has been fixed.

If that doesn't work, then either continuing down the path you're currently on or (after having made a system image backup, and separate user data backup for all accounts) Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Fetch the Win10 ISO File (since you'll already have the ISO file from having tried the repair install) is often the simplest fix.

Yes, it does mean you'll have to reinstall your software and, perhaps, some drivers, but at least you know you have a clean and fully functioning Windows 10 instance on which you're building. Right now, you don't, and likely won't, either.

Thanks, yeah was trying to avoid the clean reinstall route as its a 11 year old system with lots and lots of applications and their settings and customizations on it. I had thought by upgrading to the 20H2 Windows 10 feature release I was getting a notch below that final solution, but that didn't change anything on the symptoms. I'm not sure if that's the same code execution path as what you're describing by a Repair Install though?

 

[xevious]

Make a new restore point:
Create System Restore Point in Windows 10


Make a free backup image:
It’s our business to protect your data
Backup and Restore with Macrium Reflect


This is a trial and error step:
Change Device Installation Timeout in Windows (Fix 0x000005B4 Error) - Tech Journey

Device install process timeout exceeded.

This has taken some time to trial and error out ;-) The reg keys were not there but I added them following the link (I have Home edition so no policy editor available). I have tried values of 5, 15 and 30 minutes. They are being recognized as the driver installation programs get hung at wait times proportional to these timeout values being tried. But no change in the outcome.

 

[xilolee]

Click windows start button, type (copy/paste): systempropertiesadvanced.exe
Press enter and click yes to the user account window that should appear.
Click Environment variables.
Under the system variables frame, double-left click the PATH variable.
Click the edit text button.
In the edit box, to the right of Variable value:, remove everything and paste this string:

c:\program files (x86)\common files\microsoft shared\windows live; c:\program files (x86)\common files\oracle\java\javapath; c:\program files (x86)\intel\icls client\; c:\program files (x86)\intel\intel(r) management engine components\dal; c:\program files (x86)\intel\intel(r) management engine components\ipt; c:\program files (x86)\intel\opencl sdk\3.0\bin\x64; c:\program files (x86)\intel\opencl sdk\3.0\bin\x86; c:\program files (x86)\windows kits\10\windows performance toolkit\; c:\program files (x86)\windows live\shared; c:\program files\common files\microsoft shared\windows live; c:\program files\intel\icls client\; c:\program files\intel\intel(r) management engine components\dal; c:\program files\intel\intel(r) management engine components\ipt; c:\programdata\oracle\java\javapath; c:\windows; c:\windows\system32; c:\windows\system32\openssh\; c:\windows\system32\wbem; c:\windows\system32\windowspowershell\v1.0

Be careful: it's one line only.
Then click Ok thrice.
Then re-try the previous command (sorry, it was delete and not del):

sc delete easyanticheat

 

[xevious]

Click windows start button, type (copy/paste): systempropertiesadvanced.exe
Press enter and click yes to the user account window that should appear.
Click Environment variables.
Under the system variables frame, double-left click the PATH variable.
Click the edit text button.
In the edit box, to the right of Variable value:, remove everything and paste this string:

c:\program files (x86)\common files\microsoft shared\windows live; c:\program files (x86)\common files\oracle\java\javapath; c:\program files (x86)\intel\icls client\; c:\program files (x86)\intel\intel(r) management engine components\dal; c:\program files (x86)\intel\intel(r) management engine components\ipt; c:\program files (x86)\intel\opencl sdk\3.0\bin\x64; c:\program files (x86)\intel\opencl sdk\3.0\bin\x86; c:\program files (x86)\windows kits\10\windows performance toolkit\; c:\program files (x86)\windows live\shared; c:\program files\common files\microsoft shared\windows live; c:\program files\intel\icls client\; c:\program files\intel\intel(r) management engine components\dal; c:\program files\intel\intel(r) management engine components\ipt; c:\programdata\oracle\java\javapath; c:\windows; c:\windows\system32; c:\windows\system32\openssh\; c:\windows\system32\wbem; c:\windows\system32\windowspowershell\v1.0

Be careful: it's one line only.
Then click Ok thrice.
Then re-try the previous command (sorry, it was delete and not del):

sc delete easyanticheat

Thanks, delete service success message this time.

 

[britechguy]

I'm not sure if that's the same code execution path as what you're describing by a Repair Install though?

The difference between a feature update and a repair install all lies in what version of Windows 10 is already running on the system. If, say, you're running Version 20H2, and follow the directions using the ISO for 20H2, that's a repair install. You have the same version already running as the ISO file would put on.

If, for example, you were running Version 2009, and used the ISO for 20H2, that's a Feature Update.

Since there's absolutely nothing to lose with a Repair Install, if what you did previously was an actual Feature Update, probably via Windows Update (though you could have used another method), it's certainly not going to hurt to do a Repair Install.

For myself, if doing an actual repair install does not fix the issue, what you've described so far indicates a Windows 10 instance that has significant corruptions. I would not trust it going forward even if you do get the issues at hand fixed. My typical statement is, "You can't build a solid foundation on quicksand." There are times when it really makes more sense to go the route that's more painful in the short term to prevent ongoing and recurring pain that could be avoided entirely. That choice, however, lies with you. You are receiving solid assistance from @xilolee as far as trying to do deep under the hood diagnostics and very targeted repairs.

 

[xevious]

The difference between a feature update and a repair install all lies in what version of Windows 10 is already running on the system. If, say, you're running Version 20H2, and follow the directions using the ISO for 20H2, that's a repair install. You have the same version already running as the ISO file would put on.

If, for example, you were running Version 2009, and used the ISO for 20H2, that's a Feature Update.

Since there's absolutely nothing to lose with a Repair Install, if what you did previously was an actual Feature Update, probably via Windows Update (though you could have used another method), it's certainly not going to hurt to do a Repair Install.

For myself, if doing an actual repair install does not fix the issue, what you've described so far indicates a Windows 10 instance that has significant corruptions. I would not trust it going forward even if you do get the issues at hand fixed. My typical statement is, "You can't build a solid foundation on quicksand." There are times when it really makes more sense to go the route that's more painful in the short term to prevent ongoing and recurring pain that could be avoided entirely. That choice, however, lies with you. You are receiving solid assistance from @xilolee as far as trying to do deep under the hood diagnostics and very targeted repairs.

I can give that repair path a go then following the linked doc. It's worth a shot thx. Sincerely appreciate everyone taking a look here.

 

[xilolee]

Your desktop board manual says:

Audio: 10-channel (7.1 + 2) Intel High Definition Audio via the Realtek ALC892 audio codec.

Try to download and install R2.82 realtek audio drivers for windows 10 x64.

If that won't work (i.e., you can't download it), go to PC Audio Codecs > High Definition Audio Codecs Software - REALTEK and click the download icon near "Vista, Windows7, Windows8, Windows8.1, Windows10 Driver (32/64bits) Driver only (Executable file)...".
It asked my email and to resolve a captcha to download it.

Let me know what the installation says.

 

[zbook]

I had thought by upgrading to the 20H2 Windows 10 feature release I was getting a notch below that final solution, but that didn't change anything on the symptoms.

Which windows versions were working without the current driver problems (Windows 7, 8.1, 10 (1511, 1607, 1703 > 20H1)?
And when were the last few upgrades performed?

 

[britechguy]

I can give that repair path a go then following the linked doc. It's worth a shot thx. Sincerely appreciate everyone taking a look here.

Yep, but for complete clarity for future readers I'll give links to the pertinent instruction sets again:

Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file, which is the first step, as you lose nothing by doing one and it often fixes the issue

Then, if that, or all other interventions don't, and you have made a full system image backup of your current Windows 10 installation along with a separate full user data backup for all accounts, as well as having gathered the installers for software you need to have reinstalled promptly, you move along to:

Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Fetch the Win10 ISO File, and since you will have already fetched the ISO file to try the Repair Install/Feature Update, you can skip the steps related to that and move straight to creating the USB install media using Rufus or a similar utility of your choosing.

At this point I will bow out unless you request additional help at a later point in time.

 

[xevious]

Which windows versions were working without the current driver problems (Windows 7, 8.1, 10 (1511, 1607, 1703 > 20H1)?
And when were the last few upgrades performed?

It started mid last year, one of the Windows 10 updates. So all Windows 10 flavors but I don't recall all their build numbers. I do stay current though.

 

[xevious]

Your desktop board manual says:


Try to download and install R2.82 realtek audio drivers for windows 10 x64.

If that won't work (i.e., you can't download it), go to PC Audio Codecs > High Definition Audio Codecs Software - REALTEK and click the download icon near "Vista, Windows7, Windows8, Windows8.1, Windows10 Driver (32/64bits) Driver only (Executable file)...".
It asked my email and to resolve a captcha to download it.

Let me know what the installation says.

Bombed out, same 0xcfffffff error. Thanks though.

 

[xilolee]

• Download and unzip R2.82 realtek audio driver x86-x64 Win7_Win8_Win81_Win10.zip.
• Open Device manager
• Open the node Sound video and game controllers
• Double-left-click your intel HD audio (or whatever it is called)
• Switch to the Driver tab
• Click Update driver button
• Click Browse my computer for drivers button
• Browse to the previous unzipped folder Win7_Win8_Win81_Win10_R282
• Click ok and next
• It should (try to) install the driver
• Whatever the outcome, take a screenshot (png or jpg) and post it here

 

[zbook]

It started mid last year, one of the Windows 10 updates. So all Windows 10 flavors but I don't recall all their build numbers. I do stay current though.

Each new Windows version has new and ongoing troubleshooting problems:
Resolved issues in Windows 10, version 20H2 and Windows Server, version 20H2 | Microsoft Docs
Windows 10, version 20H2 and Windows Server, version 20H2 | Microsoft Docs

Older Windows versions (iso) are available and free.

With back up images these are options:

1) continue troubleshooting the current 20H2 version

2) Clean install version 1709 or 1803
a) Install drivers
b) Test hardware / performance
c) If there are problems then clean install 1603 with drivers and test
d) If there are problems then restore the 20H2 image knowing the performance limitations

2) If 1709 or 1803 with drivers performs well then
a) backup drivers
c) upgrade to 1903 > retest
d) upgrade to 1909 > retest
e) upgrade to 20H1 > retest
f) upgrade to 20H2 > retest
g) all upgrades should allow rollbacks within 10 days

3) If any of the version by version upgrades fail then you rollback and block future upgrades
Then install applications > make a new backup image

4) Restore 20H2 > attempt driver restoration


Backup and Restore Device Drivers in Windows 10

Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)
UUP dump

 

[xevious]

Yep, but for complete clarity for future readers I'll give links to the pertinent instruction sets again:

Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file, which is the first step, as you lose nothing by doing one and it often fixes the issue

Then, if that, or all other interventions don't, and you have made a full system image backup of your current Windows 10 installation along with a separate full user data backup for all accounts, as well as having gathered the installers for software you need to have reinstalled promptly, you move along to:

Doing a Completely Clean (Re)install of Windows 10 Using Media Creation Tool to Fetch the Win10 ISO File, and since you will have already fetched the ISO file to try the Repair Install/Feature Update, you can skip the steps related to that and move straight to creating the USB install media using Rufus or a similar utility of your choosing.

At this point I will bow out unless you request additional help at a later point in time.

I did the repair install last nite. Much to my surprise, given I thought the feature updates were a complete overwrite to begin with, the ISO repair install did install all of the drivers successfully! It's not a complete repair as something of the original problem is still lingering though. As a test I attempted to update the Nvidia video driver (the Windows one is not the latest) and again I got the oxcfffff error but this repair install approach solved my immediate problem so I'm gtg with it.

Thanks everyone for the suggestions and ideas.

 

[britechguy]

I would "work my way backwards" with that Nvidia driver as far as trying to find the latest version on your computer manufacturer's support pages (or Nvidia's, if it's a custom build), and if the most recent doesn't work, then try the next oldest one, lather, rinse repeat.

But my preference for driver source is always the machine's manufacturer's support pages first, the device's support pages second, and Microsoft third.