Windows 2012 R2 w/exchange 2013 - Update Issues

B

Brian_Busnitech

Member
Joined
May 9, 2020
Posts
18
I have a 2012 R2 server with Exchange 2013 in my test lab. It runs on VMware Esxi 6.5.
Server runs fine but will not install the monthly rollup patches. It will typically install the option items like .Net updates etc.

When trying DISM to restore health it will fail


dism /online /cleanup-image /restorehealth /source:WIM:E:\sources\install.wim:2 /LimitAccess

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


As I was googling found about a hotfix KB2966828-x64, so installed it and now the error is(note mapping to another existing 2012 Server that patches with no issues to use as source files)

dism /online /cleanup-image /restorehealth /source:W:\windows


Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 0x800f0906

The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


Ran SFCFix with this log

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-05-10 19:21:10.333
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-05-10 22:14:50.728
----------------------EOF-----------------------


CBS logs were too large to upload so here is the link
CBS.zip


Not sure where to turn now so any assistance is greatly appreciated.

Thanks
 
Hi!

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4534324;KB4534297 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Hi!

Please do the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Thank you.

Please run the following command:

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

If it completes successfully, please retry updates and attach CBS.log if any fail.
 
Last edited:
I left the Dism /Online /Cleanup-Image /RestoreHealth command running and went to bed last night.
Woke up this morning to check on the server and it had rebooted after the schedule WSUS patching kicked in at 3AM. This morning server is fully patched. So not 100% if the command completed before the patches applied, but regardless it would appear all is now fine.
I thank you very much as I have been working on this on and off for a few months now.

Thanks again.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top