- Windows 8.1 and Windows RT 8.1 build on Windows 8 and Windows RT, to bring you enhancements in personalization, search, apps, the Windows Store, and cloud connectivity, and has the security and reliability features you expect from Windows. It's fast and made to work on a variety of devices—especially on the new generation of touch devices.
- Fix NET Framework 3 5 installation Error: 0x800F0906, 0x800F081F, 0x800F0907The problem occurs when trying to install Microsoft.NET Framework 3.5 on a comp.
- If while running the DISM Tool, you see DISM Error 0x800f0906, The source files could not be downloaded message, then this post will be able to help you. A few days back, we posted about the.
- For more information on specifying a source location, see MSN.com - Hotmail, Outlook, Skype, Bing, Latest News, Photos Videos DISM log file can be found at C: WINDOWS Logs DISM dism.logC: WINDOWS system32.
Error: 0x800f0906 The source files could not be downloaded. Windows Logs DISM dism.log PS C: Windows system32 sfc /scannow. Windows 8.1, and Windows Server.
Error 0x800f0906 Windows 10
![Error 0x800f0906 Windows 8.1 Dism Error 0x800f0906 Windows 8.1 Dism](/uploads/1/1/8/9/118945276/328871840.jpg)
I ran the following command on a Server 2012 R2 running WSUS:
DISM.exe /Online /Cleanup-image /Restorehealth
![Dism Dism](/uploads/1/1/8/9/118945276/620693617.png)
It failed with error 0x800F0906
Various posts online tell you that the solution for that error is to rename C:WindowsSoftwareDistributionDownload and C:WindowsSystem32catroot2 then reboot. When I did that, I broke my WSUS installation and started getting errors like these:
Log Name: Application
Source: MSSQL$MICROSOFT##WID
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: NETWORK SERVICE
Description:
Login failed for user ‘NT AUTHORITYNETWORK SERVICE’. Reason: Failed to open the explicitly specified database ‘SUSDB’. [CLIENT: <named pipe>]
Some research took me back to KB3159706. My Installed Updates doesn’t list that update, but my hunch is that it is included in a later cumulative update. So I applied (or re-applied) the “postinstall” task described in KB3159706, which I blogged about here. That got WSUS working again.
Source: MSSQL$MICROSOFT##WID
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: NETWORK SERVICE
Description:
Login failed for user ‘NT AUTHORITYNETWORK SERVICE’. Reason: Failed to open the explicitly specified database ‘SUSDB’. [CLIENT: <named pipe>]
Some research took me back to KB3159706. My Installed Updates doesn’t list that update, but my hunch is that it is included in a later cumulative update. So I applied (or re-applied) the “postinstall” task described in KB3159706, which I blogged about here. That got WSUS working again.
Fortunately, I stumbled across this article on repairing a .NET Framework 3.5 installation error. For 0x800F0906, it advises setting group policy to tell WSUS that it’s okay to download repair sources directly from Windows Update, which makes sense:
So I updated my WSUS group policy to enable Computer Configuration > Policies > Administrative Templates > System > Specify settings for optional component installation and component repair:
Error 0x800f0906 Windows 8.1 Dismissed
After that, DISM was able to complete successfully.