Windows Update and Features won't install after moving ProgramData

Solution 1:

Installation errors after moving folders like these to other drives are inevitable. I used to do it for years, and I simply learned to live with some updates' not being installed. Part of the issue may be that the All Users folder is a symlink to ProgramData. Somehow or another, Windows may be finding issue with this, which wouldn't be surprising.

Things I would try either individually or in combination with each other (after backing up your drive):

1. Recreate the All Users symlink:
   • Delete the c:\users\All Users symlink
   • Create a new c:\users\All Users symlink to the new ProgramData
2. Search through the registry for `c:\users\All Users' values and change them to your new folder.
3. Download the .NET update executable and install it (if it has a .exe extension, just double-click it. *.msu files require wusa.exe).

Solution 2:

This may not solve the problem, but here is some advice.

First it is my experience that moving major Windows folders is problematic for Windows Update. In case of need, one should only move specific sub-folders, rather than the entire folder.

Second, the first error I see in the DISM log is :

2016-06-11 18:04:34, Info   DISM  DISM Package Manager: PID=9044 TID=7848 CBS session options=0x20100! - CDISMPackageManager::Internal_Finalize
2016-06-11 18:04:38, Info   DISM  DISM Package Manager: PID=9044 TID=5548  Error in operation: (null) (CBS HRESULT=0x80070bc9) - CCbsConUIHandler::Error
2016-06-11 18:04:38, Error  DISM  DISM Package Manager: PID=9044 TID=7848 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070bc9)
2016-06-11 18:04:38, Error  DISM  DISM Package Manager: PID=9044 TID=7848 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x80070bc9)
2016-06-11 18:04:38, Error  DISM  DISM Package Manager: PID=9044 TID=7848 Failed ProcessChanges. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x80070bc9)
2016-06-11 18:04:39, Error  DISM  DISM Package Manager: PID=9044 TID=7848 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070bc9)
2016-06-11 18:04:39, Info   DISM  DISM Package Manager: PID=9044 TID=7848 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2016-06-11 18:04:39, Error  DISM  DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070BC9

The error code 0x80070bc9 is typical of Windows Update errors. This error means "the request operation failed, a system reboot is required to roll back changes made".

My recommendations are (reboot and recheck after each step) :

1. Return the ProgramData folder back to its place

2. Run the sfc /scannow command to verify system integrity as described here

3. Run the command

fsutil resource setautoreset true c:\

Then in Safe mode try to delete these files from the Command Prompt (cmd):

cd %SystemRoot%\System32\SMI\Store\Machine
attrib -s -h *
del *.blf
del *.regtrans-ms
cd %SystemRoot%\System32\config\TxR
attrib -s -h *
del /q *

4. Run the Windows Update troubleshooter

5. Last resort : Run a non-destructive re-installation (aka in-place upgrade) of Windows. This will keep your personal files and settings, installed drivers, programs and apps, and may return Windows to a fully working state. This method usually helps when nothing else resolves a Windows Update error. See the article Repair Install Windows 10 with an In-place Upgrade.

Before starting, I recommend taking good backups. It is best to also take a snapshot image of the system disk and ensure you can restore it when booting from CD or USB. AOMEI Backupper Standard Freeware is my recommended backup utility with its recovery boot CD / USB.

Solution 3:

You can try to use Windows Update instead of your install source,

See https://technet.microsoft.com/en-us/library/dn482065.aspx

If you select Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS), any attempt to add features (for example, .NET Framework 3.5) or repair the feature file store, uses Windows Update to download files. Target computers require Internet and Windows Update access for this option.

You will change this value in local system policies gpedit.msc

Computer Policy -> Computer Configuration -> Administrative Templates -> System -> Specify settings for optional component installation and component repair

And enable Contact Windows Update directly

http://www.tenforums.com/windows-updates-activation/21919-windows-update-error-0x80080005.html

This GPO enables Windows to use Windows Update to download missing installation files. You can then try to install using Control Panel, add features.