On Tue, Apr 5, 2016 at 7:39 AM, Joe Tinney <j...@joetinney.com> wrote:
>
> Wow, that got hairy fast. I'd think we'd have to work these one at a time.
>
> I've used this before to work through the CheckSUR errors: 
> https://support.microsoft.com/en-us/kb/2700601

Tried that; download the latest System Readiness Tool; says all is fine:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-04-25 10:51

<snip>

Summary:
Seconds executed: 819
 No errors detected

> I haven't seen the driver error before related to removing old updates. Was 
> this machine a P2V?

Nope, created from a VMware template.

> MS KB for that error code covers some of your steps but offers some others 
> and confirms messaging from CheckSUR: 
> https://support.microsoft.com/en-us/kb/958044

That's for Win 7 or 8; this is Win2008 R2. But I can try it, I suppose.

> I'd check device manager with a known good VM and see of there is anything 
> out of place as well.

Nope.

> If you run the cleanup tool again and you encounter the error reporting 
> message have a look manually. (File locations at the link below) You may also 
> consider customizing the WER settings on that machine: 
> https://msdn.microsoft.com/en-us/library/windows/desktop/bb513638(v=vs.85).aspx
>  . There are also Group Policy options if you prefer.
>
> Good luck!
>
> On Apr 4, 2016 12:19, "Michael Leone" <oozerd...@gmail.com> wrote:
>>
>> I've found this:
>>
>> https://superuser.com/questions/793327/sfc-found-errors-dism-named-the-errors-but-how-can-i-fix-them-on-windows-7
>>
>> which suggests to rename the 4 mis-named files. Which I can't do, due to 
>> permissions. I suppose I can add my login to the security for RWXD to that 
>> servicing\packages folder, but I'd wary of screwing something up.
>>
>> The other suggestion, to use pkgmgr /UP: to uninstall the "Unavailable 
>> repair files", but that didn't work, either.
>>
>>
>>
>>
>>
>> On Mon, Apr 4, 2016 at 11:30 AM, Michael Leone <oozerd...@gmail.com> wrote:
>>>
>>> There's definitely something wrong. The C: drive is 60G, showing 4G free. 
>>> Running cleanmgr now I see this:
>>>
>>>
>>>
>>> No way that's right. I tell it to clean up just the system queued error 
>>> reports, and then I get back only 8G free space, not 45G ...
>>>
>>> Then I tell it to clean up the Windows Update Cleanup. It proceeds to do it 
>>> normally (says it's cleaning up). Then it finishes, and I reboot (since the 
>>> cleanup only happens at reboot). This is where it says that it fails, and 
>>> is reverting changes (for like 30 minutes ...). After it finally reboots, 
>>> the CBS log is huge (literally; over a million lines).
>>>
>>>
>>> I can pick out these, that seem to be errors:
>>>
>>> 2016-04-04 10:41:04, Info                  CBS    Doqe:   q-uninstall: Inf: 
>>> usbport.inf, Ranking: 2, Device-Install: 1, Key: 1, Identity: usbport.inf, 
>>> Culture=neutral, Type=driverUpdate, Version=6.1.7601.17586, 
>>> PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, 
>>> versionScope=NonSxS
>>> 2016-04-04 10:41:04, Info                  CBS    Doqe:   q-uninstall: Inf: 
>>> usb.inf, Ranking: 2, Device-Install: 1, Key: 2, Identity: usb.inf, 
>>> Culture=neutral, Type=driverUpdate, Version=6.1.7601.17586, 
>>> PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, 
>>> versionScope=NonSxS
>>> 2016-04-04 10:41:04, Info                  CBS    Doqe:   q-uninstall: Inf: 
>>> wdmaudio.inf, Ranking: 2, Device-Install: 0, Key: 3, Identity: 
>>> wdmaudio.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18276, 
>>> PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, 
>>> versionScope=NonSxS
>>> 2016-04-04 10:41:04, Info                  CBS    Perf: Doqe: Uninstall 
>>> started.
>>> 2016-04-04 10:41:04, Info                  CBS    Doqe: [Forward] 
>>> Uninstalling driver updates, Count 3
>>> 2016-04-04 10:41:04, Info                  CBS    
>>> DriverUpdateUninstallUpdates failed [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
>>> 2016-04-04 10:41:04, Error                 CBS    Doqe: Failed uninstalling 
>>> driver updates [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
>>> 2016-04-04 10:41:04, Info                  CBS    Perf: Doqe: Uninstall 
>>> ended.
>>> 2016-04-04 10:41:04, Info                  CBS    Failed uninstalling 
>>> driver updates [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
>>> 2016-04-04 10:41:04, Error                 CBS    Shtd: Failed while 
>>> processing non-critical driver operations queue. [HRESULT = 0x80070490 - 
>>> ERROR_NOT_FOUND]
>>> 2016-04-04 10:41:04, Info                  CBS    Shtd: Rolling back KTM, 
>>> because drivers failed.
>>>
>>> Then a huge series like this:
>>>
>>> 2016-04-04 10:43:07, Info                  CBS    Startup: Package: 
>>> Microsoft-Windows-IE-Hyphenation-Package-English~31bf3856ad364e35~amd64~~6.2.9200.16437
>>>  completed startup processing, new state: Superseded, original: Superseded, 
>>> targeted: Absent.  hr = 0x80070490
>>> 2016-04-04 10:43:07, Info                  CBS    WER: Generating failure 
>>> report for package: 
>>> Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437,
>>>  status: 0x80070490, failure source: CBS Other, start state: Superseded, 
>>> target state: Absent, client id: Deepclean
>>> 2016-04-04 10:43:07, Info                  CBS    Failed to query 
>>> DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - 
>>> ERROR_FILE_NOT_FOUND]
>>> 2016-04-04 10:43:07, Info                  CBS    Failed to add 
>>> %windir%\winsxs\pending.xml to WER report because it is missing.  
>>> Continuing without it...
>>> 2016-04-04 10:43:07, Info                  CBS    Failed to add 
>>> %windir%\winsxs\pending.xml.bad to WER report because it is missing.  
>>> Continuing without it...
>>> 2016-04-04 10:43:40, Info                  CBS    SQM: Reporting package 
>>> change completion for package: 
>>> Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437,
>>>  current: Superseded, original: Superseded, target: Absent, status: 
>>> 0x80070490, failure source: CBS Other, failure details: "(null)", client 
>>> id: Deepclean, initiated offline: False, execution sequence: 1125, first 
>>> merged sequence: 1125
>>> 2016-04-04 10:43:40, Info                  CBS    SQM: Failed to initialize 
>>> Win SAT assessment. [HRESULT = 0x80040154 - Unknown Error]
>>> 2016-04-04 10:43:40, Info                  CBS    SQM: average disk 
>>> throughput datapoint is invalid [HRESULT = 0x80040154 - Unknown Error]
>>> 2016-04-04 10:43:40, Info                  CBS    SQM: Upload requested for 
>>> report: 
>>> PackageChangeEnd_Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437,
>>>  session id: 142862, sample type: Standard
>>> 2016-04-04 10:43:40, Info                  CBS    SQM: Ignoring upload 
>>> request because the sample type is not enabled: Standard
>>>
>>>
>>> Dunno what's up with those driver fails; this is a VMware VM (and the 
>>> VMware Tools are up to date, and there is no USB controller in the VMware 
>>> hardware settings). I'm assuming that "Rolling back KTM" is the cause of 
>>> the failure, and the "reverting changes" ... which apparently aren't really 
>>> being written to the error logs properly.
>>>
>>> Found this, in the "CheckSUR.log":
>>>
>>> =================================
>>> Checking System Update Readiness.
>>> Binary Version 6.1.7601.18741
>>> 2016-04-01 14:10
>>>
>>> Checking Windows Servicing Packages
>>>
>>> Checking Package Manifests and Catalogs
>>> (f) CBS MUM Corrupt 0x00000000 
>>> servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
>>>  Expected file name 
>>> Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum
>>>  does not match the actual file name
>>> (f) CBS MUM Corrupt 0x00000000 
>>> servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
>>>  Expected file name 
>>> Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum
>>>  does not match the actual file name
>>> (f) CBS MUM Corrupt 0x00000000 
>>> servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
>>>  Expected file name 
>>> Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum
>>>  does not match the actual file name
>>> (f) CBS MUM Corrupt 0x00000000 
>>> servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
>>>  Expected file name 
>>> Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum
>>>  does not match the actual file name
>>>
>>> Checking Package Watchlist
>>>
>>> Checking Component Watchlist
>>>
>>> Checking Packages
>>>
>>> Checking Component Store
>>>
>>> Summary:
>>> Seconds executed: 752
>>>  Found 4 errors
>>>   CBS MUM Corrupt Total count: 4
>>>
>>> Unavailable repair files:
>>> servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
>>> servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
>>> servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
>>> servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
>>> servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
>>> servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
>>> servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
>>> servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
>>>
>>> (w) Unable to get system disk properties 0x0000045D 
>>> IOCTL_STORAGE_QUERY_PROPERTY Disk Cache
>>>
>>>
>>> On Fri, Apr 1, 2016 at 10:54 PM, Joe Tinney <j...@joetinney.com> wrote:
>>>>
>>>> Michael,
>>>>
>>>> Have you checked CBS.log for errors?
>>>>
>>>> Good luck,
>>>> Joe Tinney
>>>>
>>>> On Apr 1, 2016 2:55 PM, "Michael Leone" <oozerd...@gmail.com> wrote:
>>>>>
>>>>> I'm trying to clean up the old Windows Update files on one of my
>>>>> Win2008 R2 servers. So I run the cleanmgr command, and choose the
>>>>> option to do so. (this server has that update to allow this),
>>>>>
>>>>> And then the server chugs along for a while, as it should. Then I
>>>>> reboot it, as that's when the actual cleanup happens. It starts to do
>>>>> it ("Configuring Windows Updates"). Then it says "Failure configuring
>>>>> Windows updates", and "reverting changes".
>>>>>
>>>>> And I can't figure out why. I see no entries in the Event Logs, about
>>>>> anything failing. I tried "dism /online /cleanup-image /scanhealth",
>>>>> and it complained about 4 misnamed files, but that's all.
>>>>>
>>>>> So how can I figure out why it's failing, and this (hopefully) fix it?
>>>>> I'd like my 6G disk space back, please. :-)
>>>>>
>>>>>
>>>
>>


Reply via email to