Update KB3000850 fails to install

Hi again Robert,

Sorry, I got mixed up with cmd and powershell.

I re-ran the original command dir/a-d/b/s *16407* | find /i /v ".manifest" | clip on a cmd line but it didn't appear to return any results.

Here's the results of dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue | Where-Object -FilterScript {!$_.FullName.EndsWith(".manifest")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Length FullName

---

       C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Reac207edc4d#\777b416407de8291e1685a4d815e5b57

       C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1

       C:\WINDOWS\WinSxS\amd64_intelpep.inf_31bf3856ad364e35_6.3.9600.16407_none_b5bc98d7fccb5ce6

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..atibility-assistant_31bf3856ad364e35_6.3.9600.16407_none_24de6842f6da7242

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..bility-assistant-ui_31bf3856ad364e35_6.3.9600.16407_none_39de10a89282150d

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..ence-infrastructure_31bf3856ad364e35_6.3.9600.16407_none_c628e5ed206d46db

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-appx-deployment-client_31bf3856ad364e35_6.3.9600.16407_none_a6f9b19bae09dffb

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-dui70_31bf3856ad364e35_6.3.9600.16407_none_48cc91ffd1ce370f

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-e..host-shellnamespace_31bf3856ad364e35_6.3.9600.16407_none_95b2639d38eb8fd8

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-e..namespace.resources_31bf3856ad364e35_6.3.9600.16407_en-gb_8e36f83f43c7bbec

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-e..riseclientsync-host_31bf3856ad364e35_6.3.9600.16407_none_bf2b5d1a4a48280a

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-globalization_31bf3856ad364e35_6.3.9600.16407_none_042b8cd1b2a4e905

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-mediaviewer.resources_31bf3856ad364e35_6.3.9600.16407_en-gb_f468723d2ca10172

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-oobe-machine-plugins_31bf3856ad364e35_6.3.9600.16407_none_c04e1573dae506d4

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.16407_none_8d21a05a74a76028

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-psmcoreserver_31bf3856ad364e35_6.3.9600.16407_none_9be9460656382b1e

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..client-ui.resources_31bf3856ad364e35_6.3.9600.16407_en-gb_ccf92227d6e4beac

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..on-onlineid-runtime_31bf3856ad364e35_6.3.9600.16407_none_39a0d3389005d9f3

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-settingsync_31bf3856ad364e35_6.3.9600.16407_none_8232a0bccde86f49

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-twinapi_31bf3856ad364e35_6.3.9600.16407_none_ac7511533a51dff8

       C:\WINDOWS\WinSxS\amd64_microsoft-windows-twinui.resources_31bf3856ad364e35_6.3.9600.16407_en-gb_183bd1ec7a3afca0

       C:\WINDOWS\WinSxS\amd64_wdma_bt.inf.resources_31bf3856ad364e35_6.3.9600.16384_en-us_8bbc16407af64369

       C:\WINDOWS\WinSxS\amd64_windows-id-connecte..t-provider-wlidprov_31bf3856ad364e35_6.3.9600.16407_none_3099d640567975ca

       C:\WINDOWS\WinSxS\Temp\InFlight\214f9309b787cf0102000000a00c280a\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

       C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-a..ence-infrastructure_31bf3856ad364e35_6.3.9600.16407_none_d07d903f54ce08d6

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-appx-deployment-client_31bf3856ad364e35_6.3.9600.16407_none_b14e5bede26aa1f6

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-e..host-shellnamespace_31bf3856ad364e35_6.3.9600.16407_none_a0070def6d4c51d3

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-globalization_31bf3856ad364e35_6.3.9600.16407_none_0e803723e705ab00

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-performancetoolsgui_31bf3856ad364e35_6.3.9600.16407_none_97764aaca9082223

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-s..on-onlineid-runtime_31bf3856ad364e35_6.3.9600.16407_none_43f57d8ac4669bee

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-twinapi_31bf3856ad364e35_6.3.9600.16407_none_b6c9bba56eb2a1f3

       C:\WINDOWS\WinSxS\wow64_microsoft-windows-twinui.resources_31bf3856ad364e35_6.3.9600.16407_en-gb_22907c3eae9bbe9b

       C:\WINDOWS\WinSxS\wow64_windows-id-connecte..t-provider-wlidprov_31bf3856ad364e35_6.3.9600.16407_none_3aee80928ada37c5

       C:\WINDOWS\WinSxS\x86_microsoft-windows-a..bility-assistant-ui_31bf3856ad364e35_6.3.9600.16407_none_ddbf7524da24a3d7

       C:\WINDOWS\WinSxS\x86_microsoft-windows-dui70_31bf3856ad364e35_6.3.9600.16407_none_ecadf67c1970c5d9

       C:\WINDOWS\WinSxS\x86_microsoft-windows-settingsync_31bf3856ad364e35_6.3.9600.16407_none_26140539158afe13

... and here's the results of dir -Re -Fi "*Flash*" -Fo  -ErrorAction:SilentlyContinue  | Where-Object -FilterScript {$_.FullName.Contains("\Sys")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

  Length FullName

  ------ --------

    3718 C:\WINDOWS\System32\Tasks\Adobe Flash Player Updater

    9580 C:\WINDOWS\System32\catroot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cat

         C:\WINDOWS\System32\Macromed\Flash

         C:\WINDOWS\SysWOW64\Macromed\Flash

         C:\WINDOWS\System32\config\systemprofile\AppData\Roaming\Adobe\Flash Player

  939224 C:\WINDOWS\SysWOW64\Flash.OCX

18617824 C:\WINDOWS\SysWOW64\Macromed\Flash\Flash.ocx

23878624 C:\WINDOWS\System32\Macromed\Flash\Flash.ocx

   10478 C:\WINDOWS\System32\Macromed\Flash\FlashInstall.log

   13934 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashInstall.log

     856 C:\WINDOWS\SysWOW64\Macromed\Flash\flashplayer.xpt

  714208 C:\WINDOWS\SysWOW64\FlashPlayerApp.exe

  106976 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

 1880752 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerPlugin_15_0_0_239.exe

  267440 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

   11561 C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9\flashusb.cat

    8178 C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9\flashusb.inf

         C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9

   11680 C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9\flashusb.PNF

   19968 C:\WINDOWS\System32\DriverStore\FileRepository\flashusb.inf_amd64_d97dba44a43ee5a9\FlashUSB.sys

  549856 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil_ActiveX.dll

  606688 C:\WINDOWS\System32\Macromed\Flash\FlashUtil_ActiveX.dll

  898528 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil_ActiveX.exe

  573920 C:\WINDOWS\System32\Macromed\Flash\FlashUtil_ActiveX.exe

  855216 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_15_0_0_239_Plugin.exe

  540848 C:\WINDOWS\System32\Macromed\Flash\FlashUtil64_15_0_0_239_Plugin.exe

    1215 C:\WINDOWS\System32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts\Kodak Flash Drive.lnk

Thanks once again for your patience and help with this.

Regards,

Richard

I re-ran the original command dir/a-d/b/s *16407* | find /i /v ".manifest" | clip on a cmd line but it didn't appear to return any results.

didn't appear to return any resultsRemember that clip puts the result into the Clipboard so the "unwritten fourth stage" of that pipeline was to be opening a Notepad window and doing a Ctrl-v in it.  So, just to clarify the result, was that done?   In my case it is true: when I Paste into Notepad I see nothing added but I was hoping that we would see some matching file information for yours.  OTOH the next attempt at a Powershell equivalent also failed so I'm not sure what I'm missing (or even thinking that we would be able to see).

Here's the results of dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue | Where-Object -FilterScript {!$_.FullName.EndsWith(".manifest")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

No lengths?  What am I missing?  What was I thinking we would see?

... and here's the results of dir -Re -Fi "*Flash*" -Fo  -ErrorAction:SilentlyContinue  | Where-Object -FilterScript {$_.FullName.Contains("\Sys")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

That shows you have a lot more modules for that build level left than I do but I don't know who is right or whether it matters if there is a discrepancy.   DISM seems to think so--or have I got that wrong too?   ; }

On review it looks like most of the difference might be because you have some real Adobe stuff, e.g. more than the embedded Flash.  I wonder if uninstalling that would help?  And why is it being allowed into the System directories anyway?

Strangely that 16407 build number doesn't mean anything to Adobe it seems

(Google search for

    16407 flash site:adobe.com

)

• results are inconclusive.

Here is an attempt to summarize my thinking about all this so far:

1. Your DISM CheckSUR showed us that it thought you were either missing some modules concerning 16407 for Flash and  16384 for dssec or that the ones you had were not useful for repair purposes.
2. Your first search for Flash* modules shows that you have consistency at the 17495 level but perhaps inconsistency at a lower or non-17495 level.  I don't understand why DISM cares about this.  As long as you can repair at the current level it should be OK I would think.  Perhaps it is trying also to check for the case that you might uninstall the current level and go back a level and then potentially need to be able to repair that?  Going all the way back to the beginning with that goal for long update chains could be increasingly unlikely to succeed and unnecessary IMO.
3. Ditto for the dssec.dat example.  Consistency at the current 17415 level, possible inconsistency due to compression at the base level.  Why can't DISM fix that at least?
4. The 16407 Flash modules that DISM reported as inconsistent don't exist but I don't have them either so "So what?"  You may have some .manifest files which are being found at this level that are causing this but we can't look at those even if we could find them because they are compressed.  How helpful!
5. I guess you had better hope that MS sees these discrepancies and puts something into the next update package which fixes them.  Otherwise in case someone suggests a Refresh I think there would be a smaller step possible using an obscure and controversial DISM option:  /StartComponentCleanup [/ResetBase]

http://technet.microsoft.com/en-us/library/hh825265.aspx

In fact, in the case of dssec.dat I suspect you are already half-way into what /StartComponentCleanup would achieve anyway.  So, it's probably the /ResetBase  which is the really controversial option.  And perhaps that one happened half-way too because it would  probably explain the repair files which are entirely "missing".

Now I'm wondering if we have been sidetracked by the CheckSUR report.  Does that happen automatically or is it something that you did?  E.g. your real objective is to get the update installed so having DISM noticing that there is "corruption" in your WinSxS could be a red herring leading us away from analyzing why the update won't install.

HTH

Robert

---

What am I missing?  What was I thinking we would see?

Oops.   I was excluding .manifests because they were the only thing that I was seeing but by excluding them we are also preventing the display of ones which you might have that are related to Flash.  So, let's change the filter to see if you do at least have one of those.

For a cmd window.  I'm not going to bother with the Clip because I think there should only be one

C:\windows>dir/a/b/s *16407*	find /i "flash"

and the Powershell equivalent should be

dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue	Where-Object -FilterScript {$_.FullName.Contains("flash")}	Sort-Object Name, LastWriteTime	ft Length, FullName -AutoSize

I'm not sure what this is going to achieve but think it is at least more relevant than the exclusion filter I had you trying before.  Otherwise, why is DISM looking for this build version?

Hi Robert,

I'll be honest, with the dir/a-d/b/s *16407* | find /i /v ".manifest" | clipcommand I did forget to copy the results to notepad but I did run it again, opened notepad, did ctrl-v but still nothing. For the command dir/a/b/s *16407* | find /i "flash" the results are :

C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1

C:\Windows\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

C:\Windows\WinSxS\Manifests\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1.manifest

C:\Windows\WinSxS\Manifests\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc.manifest

C:\Windows\WinSxS\Temp\InFlight\214f9309b787cf0102000000a00c280a\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

... and for PS command dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue  | Where-Object -FilterScript {$_.FullName.Contains("flash")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Length FullName

---

       C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1

2242   C:\WINDOWS\WinSxS\Manifests\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1.manifest

       C:\WINDOWS\WinSxS\Temp\InFlight\214f9309b787cf0102000000a00c280a\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

       C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

2406   C:\WINDOWS\WinSxS\Manifests\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc.manifest

I agree that the DISM errors could be a red herring. Looking again at the original error which I found in the Event Viewer (in the Windows Logs\System) section:

Event ID: 7023

Source: Service Control Manager

The Windows Modules Installer service terminated with the following error:

The system cannot find the path specified.

The rest of the error is :

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7023</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2014-11-24T14:08:50.530840400Z" />

    <EventRecordID>68714</EventRecordID>

    <Correlation />

    <Execution ProcessID="656" ThreadID="7264" />

    <Channel>System</Channel>

    <Computer>computer</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Windows Modules Installer</Data>

    <Data Name="param2">%%3</Data>

    <Binary>540072007500730074006500640049006E007300740061006C006C00650072000000</Binary>

  </EventData>

</Event>

Now, maybe the path that cannot be found is http://schemas.microsoft.com/win/2004/08/events/event and I've seen suggestions on other forums that this could be a Trojan. I have my doubts in this case because I run Norton 360 (I know no anti-virus software is infallible but I know Norton is considered one of the more thorough) and run weekly full system scans and this has never come up. I'm also pretty careful about where I install software from. I hope this might shed some light on things.

Regards,

Richard

... and for PS command dir -Re -Fi "*16407*" -Fo  -ErrorAction:SilentlyContinue  | Where-Object -FilterScript {$_.FullName.Contains("flash")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize :

Length FullName

---

       C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1

2242   C:\WINDOWS\WinSxS\Manifests\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_1cb7c6353d4303e1.manifest

       C:\WINDOWS\WinSxS\Temp\InFlight\214f9309b787cf0102000000a00c280a\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

       C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc

2406   C:\WINDOWS\WinSxS\Manifests\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc.manifest

So as I suspected you have .manifest files only about Flash for that build version.  So DISM is being stupid IMO and should clean this up and not complain about it.  Certainly not a good reason to hold up an update if that is what is happening.  Unfortunately I don't know enough about the WinSxS file structure to know whether you can just eliminate the orphan .manifest and thus eliminate the problem.  I think it would help if we could just browse the .manifest (the way we used to be able to).

I agree that the DISM errors could be a red herring. Looking again at the original error which I found in the Event Viewer (in the Windows Logs\System) section:

    <TimeCreated SystemTime="2014-11-24T14:08:50.530840400Z" />

That doesn't look like the right timestamp.   I think you will need to look back further in the CBS.log (or relevant archived portion) within the correct timestamp context for more clues about the update failure.

HTH

Robert

---