Update KB3000850 fails to install

Anonymous
2014-11-26T14:09:39+00:00

Hi there,

I have a problem installing update KB3000850. It downloads and appears to install OK until the computer restarts to complete the installation. It gets to about 8% of configuring windows updates and then I get the following message:

failure configuring windows

undoing changes

The computer restarts and is usable. I don't know a great deal about windows error reporting but I checked the C:\Windows\Logs\CBS\CBS log and found the following message:

CBS Failed installing driver updates [HRESULT - 0x80070003 - ERROR_PATH_NOT_FOUND]

I checked the Event Viewer and found the following message 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.

I have no idea which path it cannot find. I have tried running the SFC and DISM commands and have tried the Windows Update Automated Troubleshooter but none of these seem to fix it. I understand there is a problem with the Avast anti-virus software but I am running Norton 360. I am using Classic Shell and am not sure if that is causing the problem but don't want to uninstall it if the error is being caused by something else.

Any help or advice would be most gratefully received.

Thanks in advance,

Richard

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

110 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-12-06T13:24:41+00:00

    Hi Robert,

    I tried the DISM command again, same errors.

    I also tried the command:

    C:\Windows>dir/a-d/b/s *16407* | find /i /v ".manifest" | clip

    but got the following error:

    dir/a-d/b/s : The term 'dir/a-d/b/s' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    At line:1 char:1

    • dir/a-d/b/s *16407* | find /i /v ".manifest" | clip 
    •

        + CategoryInfo          : ObjectNotFound: (dir/a-d/b/s:String) [], CommandNotFoundException

        + FullyQualifiedErrorId : CommandNotFoundException

    I haven't used the dir command since something like 1990 (when things were way simpler) but I added a space so it was like:

    C:\Windows>dir /a-d/b/s *16407* | find /i /v ".manifest" | clip

    but then got the following error:

    dir : Cannot find path 'C:\a-d\b\s' because it does not exist.

    At line:1 char:1

    • dir /a-d/b/s *16407* | find /i /v ".manifest" | clip 
    •

        + CategoryInfo          : ObjectNotFound: (C:\a-d\b\s:String) [Get-ChildItem], ItemNotFoundException

        + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

    FIND: Parameter format not correct

    It's probably a command syntax error, right?

    Regards,

    Richard

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-04T20:07:35+00:00

    Here are the results of that command:

    PS C:\WINDOWS> dir -Re -Fi "*16407*" | Where-Object -FilterScript {!$_.FullName.EndsWith(".manifest")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize

    Interesting!  It isn't doing what I expected it to.  Back to the drawing board.  I was thinking we were doing the equivalent of a  dir/a/b/s  *16407*   which would find some modules which happened to have that string in their path and then since I saw some ending with .manifest I didn't want to show those.  But evidently Powershell is just stopping when it finds a path with that pattern in it.  Otherwise where are the Flash* modules that we saw before?  Also, no Length fields were reported in what your search found.

    Has your WinSxS been cleaned up now so that you don't have any more of those?  E.g., is the DISM still reporting the same errors?

    Just to make sure that I'm not missing something by using Powershell please try this cmd window pipeline instead.  It will show only file names but when I do it I get no files (the first stage proves that the .manifest are files but I am stripping them by the second stage.)  Note that the last (unwritten, fourth) "stage" of this pipeline is manual:  Paste the output into a Notepad window to examine it--easier than trying to do that there than in a cmd window regardless of its buffer size.

    C:\Windows>dir/a-d/b/s *16407* find /i /v ".manifest" clip

    And again, in retrospect I realize that I could have given you a Powershell equivalent which eliminated the directories first too.  Sorry about that.

    I think the link you provided for Suwii's problem is actually for this page but I did a search and found that page. Suwii is definitely more technically knowledgeable than myself but it seems that was a permissions problem.

    Good grief.  I have never done that before.  Oops.  Thanks.  I'll fix that.  What I was hoping you would notice is the technique which was used to resolve the errors which DISM reported.  E.g. find a source of the missing modules, somehow, somewhere and install it so that it can be referenced by DISM's /source: operand.  But maybe WU has beaten us to that goal and already fixed those problems.

    What's next?   ; )

    HTH

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-04T18:43:52+00:00

    Hi Robert,

    Thanks again for your help. Here are the results of that command:

    PS C:\WINDOWS> dir -Re -Fi "*16407*" | Where-Object -FilterScript {!$_.FullName.EndsWith(".manifest")} | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize

    dir : Access to the path 'C:\WINDOWS\System32\LogFiles\WMI\RtBackup' is denied.

    At line:1 char:1

    • dir -Re -Fi "*16407*" | Where-Object -FilterScript {!$_.FullName.EndsWith(".mani ... 
    •

        + CategoryInfo          : PermissionDenied: (C:\WINDOWS\Syst...es\WMI\RtBackup:String) [Get-ChildItem], UnauthorizedAccessException

        + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand

    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

    I think the link you provided for Suwii's problem is actually for this page but I did a search and found that page. Suwii is definitely more technically knowledgeable than myself but it seems that was a permissions problem.

    Regards,

    Richard

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-04T03:51:06+00:00

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

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

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

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

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

    The dssec.dat results:

    Length FullName

    215943 C:\WINDOWS\System32\dssec.dat

    215943 C:\WINDOWS\SysWOW64\dssec.dat

    215943 C:\WINDOWS\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_4b70d269d045459a\dssec.dat

    215943 C:\WINDOWS\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_ef5236e617e7d464\dssec.dat

    215943 C:\WINDOWS\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_ef059c0a182167dc\dssec.dat

      8489 C:\WINDOWS\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_4b24378dd07ed912\dssec.dat

    Good work.   So now you can see what the problem is, although I still don't understand why DISM is not sorting it out for you:  all of those "missing payloads" that were being wanted are either compressed or missing entirely.   So presumably they have to be either decompressed (somehow) or uncompressed copies of the same things downloaded from somewhere and installed (somehow). 

    Did you see SuWii's good work figuring out how to do that for a similar circumstance?

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3

    If I had been thinking we could have reduced the output by including that 16407 build version term in the search filter (though then we would have missed being able to check on the versions that you have active in the System directories).  In fact, I don't have anything like that.  So maybe we are trying to repair some things which could be removed and thereby fix the discrepancies that way?

    FWIW  here is a filter which I think would find your Flash modules but in my case just finds some directories where there are some manifests for other updates with the same build number.

    PS C:\windows> dir -Re -Fi "*16407*" Where-Object -FilterScript {!$_.FullName.EndsWith(".manifest")} Sort-Object Name, LastWriteTime ft Length, FullName -AutoSize

    HTH

    Robert

    Fixed wrong URL after Richard pointed out my error.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-12-03T19:35:11+00:00

    Hi Robert,

    I managed to run the commands you recommended and here are the results:

    PS C:\WINDOWS> dir -Re -Fi "Flash*" | Sort-Object Name, CreationTime |  ft Length, FullName -AutoSize

    dir : Access to the path 'C:\WINDOWS\System32\LogFiles\WMI\RtBackup' is denied.

    At line:1 char:1

    • dir -Re -Fi "Flash*" | Sort-Object Name, CreationTime |  ft Length, FullName -Au ... 
    •

        + CategoryInfo          : PermissionDenied: (C:\WINDOWS\Syst...es\WMI\RtBackup:String) [Get-ChildItem], UnauthorizedAccessException

        + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand

    Length   FullName

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

             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

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

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

    3936150  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_26d447a971ce3b5d\Flash.ocx

    4870842  C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_1c7f9d573d6d7962\Flash.ocx

    1254979  C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_26b0d8ed71e94052\Flash.ocx

    1631375  C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\Flash.ocx

    18617824 C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_26a909df71eea848\Flash.ocx

    23878624 C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_1c545f8d3d8de64d\Flash.ocx

    1631375  C:\WINDOWS\WinSxS\Temp\InFlight\d34050c2a709d00102000000b40fc00d\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\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

    45450    C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_26d447a971ce3b5d\FlashPlayerApp.exe

    2009     C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_26b0d8ed71e94052\FlashPlayerApp.exe

    714208   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_26a909df71eea848\FlashPlayerApp.exe

    106976   C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

    9730     C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_26d447a971ce3b5d\FlashPlayerCPLApp.cpl

    1941     C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_26b0d8ed71e94052\FlashPlayerCPLApp.cpl

    106976   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_26a909df71eea848\FlashPlayerCPLApp.cpl

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

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

    26424    C:\WINDOWS\Prefetch\FLASHPLAYERUPDATESERVICE.EXE-216D9C35.pf

    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

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

    45600    C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_26d447a971ce3b5d\FlashUtil_ActiveX.dll

    54867    C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_1c7f9d573d6d7962\FlashUtil_ActiveX.dll

    2086     C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_26b0d8ed71e94052\FlashUtil_ActiveX.dll

    2054     C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\FlashUtil_ActiveX.dll

    606688   C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_1c545f8d3d8de64d\FlashUtil_ActiveX.dll

    549856   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_26a909df71eea848\FlashUtil_ActiveX.dll

    2054     C:\WINDOWS\WinSxS\Temp\InFlight\d34050c2a709d00102000000b40fc00d\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\FlashUtil_ActiveX.dll

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

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

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

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

    260593   C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_1c7f9d573d6d7962\FlashUtil_ActiveX.exe

    614032   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17355_none_26d447a971ce3b5d\FlashUtil_ActiveX.exe

    216400   C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\FlashUtil_ActiveX.exe

    582202   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_26b0d8ed71e94052\FlashUtil_ActiveX.exe

    573920   C:\WINDOWS\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_1c545f8d3d8de64d\FlashUtil_ActiveX.exe

    898528   C:\WINDOWS\WinSxS\wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17495_none_26a909df71eea848\FlashUtil_ActiveX.exe

    216400   C:\WINDOWS\WinSxS\Temp\InFlight\d34050c2a709d00102000000b40fc00d\amd64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.17482_none_1c5c2e9b3d887e57\FlashUtil_ActiveX.exe

    48374    C:\WINDOWS\Prefetch\FLASHUTIL_ACTIVEX.EXE-C484AAB9.pf

    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

    The dssec.dat results:

    PS C:\WINDOWS> dir -Re -Fi "dssec.dat" | Sort-Object Name, LastWriteTime | ft Length, FullName -AutoSize

    dir : Access to the path 'C:\WINDOWS\System32\LogFiles\WMI\RtBackup' is denied.

    At line:1 char:1

    • dir -Re -Fi "dssec.dat" | Sort-Object Name, LastWriteTime | ft Length, FullName  ... 
    •

        + CategoryInfo          : PermissionDenied: (C:\WINDOWS\Syst...es\WMI\RtBackup:String) [Get-ChildItem], UnauthorizedAccessException

        + FullyQualifiedErrorId : DirUnauthorizedAccessError,Microsoft.PowerShell.Commands.GetChildItemCommand

    Length FullName

    215943 C:\WINDOWS\System32\dssec.dat

    215943 C:\WINDOWS\SysWOW64\dssec.dat

    215943 C:\WINDOWS\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_4b70d269d045459a\dssec.dat

    215943 C:\WINDOWS\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_ef5236e617e7d464\dssec.dat

    215943 C:\WINDOWS\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_ef059c0a182167dc\dssec.dat

      8489 C:\WINDOWS\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_4b24378dd07ed912\dssec.dat

    Once more, thanks for your continued help with this.

    Regards,

    Richard

    Was this answer helpful?

    0 comments