Hello,
Background:
VM is about 18 months old? After running perfectly for 18 months or so, this month, this VM refuses to allow monthly patches. I see nothing wrong with the machine and I would prefer not to rebuild it because installing the purpose software (I mean the reason the server was created) was painfully difficult and I don't want to have to go through that again if I don't need to.
Virtual machine running KVM flavor of hypervisor. Machine is Windows Server 2016 64-bit, 1 proc, 16gb ram, 1 hard drive (185 gb capacity with 86 gb used, 98 gb free) - zero previous issues.
Things I've done to try to remediate have been reboot, power off/power back on, download this month's KB and tried to install manually, shut off windows update service + renamed c:\windows\softwaredistribution folder to *.bak, turned windows update service back on then tried to update the KB manually w/downloaded KB file and some other tricks from the past I'm forgetting I'm sure.
1.) Run SFC Scan - after running I receive the following:
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
2.) Run dism /online /cleanup-image /restorehealth
C:\>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
The component store is repairable.
The operation completed successfully.
C:\>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
C:\>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[===========================80.0%============== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to 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
C:\>dism.exe /online /cleanup-image /restorehealth /source:\\*servername*\c$\winsxs /limitaccess
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[===========================72.7%========== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to 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
*I put the actual server name in that spot, but I also tried mounting the iso to a drive letter which I used to build the machine with originally, I also tried downloading the iso from this link from MS, etc."
3.) Run ComponentsScanner - done - see attachment.
4.) Export CBS Folder - done see attachment.
Background:
VM is about 18 months old? After running perfectly for 18 months or so, this month, this VM refuses to allow monthly patches. I see nothing wrong with the machine and I would prefer not to rebuild it because installing the purpose software (I mean the reason the server was created) was painfully difficult and I don't want to have to go through that again if I don't need to.
Virtual machine running KVM flavor of hypervisor. Machine is Windows Server 2016 64-bit, 1 proc, 16gb ram, 1 hard drive (185 gb capacity with 86 gb used, 98 gb free) - zero previous issues.
Things I've done to try to remediate have been reboot, power off/power back on, download this month's KB and tried to install manually, shut off windows update service + renamed c:\windows\softwaredistribution folder to *.bak, turned windows update service back on then tried to update the KB manually w/downloaded KB file and some other tricks from the past I'm forgetting I'm sure.
1.) Run SFC Scan - after running I receive the following:
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
2.) Run dism /online /cleanup-image /restorehealth
C:\>dism /online /cleanup-image /checkhealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
The component store is repairable.
The operation completed successfully.
C:\>dism /online /cleanup-image /scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.
C:\>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[===========================80.0%============== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to 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
C:\>dism.exe /online /cleanup-image /restorehealth /source:\\*servername*\c$\winsxs /limitaccess
Deployment Image Servicing and Management tool
Version: 10.0.14393.4169
Image Version: 10.0.14393.7426
[===========================72.7%========== ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to 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
*I put the actual server name in that spot, but I also tried mounting the iso to a drive letter which I used to build the machine with originally, I also tried downloading the iso from this link from MS, etc."
3.) Run ComponentsScanner - done - see attachment.
4.) Export CBS Folder - done see attachment.
