Windows Store - Can't Install Anything

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 10 Pro
       #1

    Windows Store - Can't Install Anything


    Hey everyone,

    So I can't install anything from the Windows Store. What happened is that I was trying to open the weather app. It would open and close down right away. So I removed it within powershell and I can't install it or any apps now. When I try to install an app, I get the following message:

    Try the download again. Something happened on our end.

    I'm on Windows 10 Pro. Version 1511. Any thoughts to what the issue might be? Any help would be appreciated.
      My Computer


  2. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #2

    Suggestions :

    #1. do a system file check to look for corrupt files. If any found, it will try to do repair.
    Right click at Start button > click Command Prompt (Admin) > at the flashing prompt, copy/paste this.......
    sfc /scannow

    > press Enter.
    It will take quite sometime.
    When finished, it will give you one of the 3 reports...............(paraphrasing)
    1. No integrity violation.
    2. Found corrupt files and repair successful.
    3. Found corrupt files but unable to repair.


    If you have report #3. Please post back. There is way to fix that.

    #2. If suggestion #1 does not help, do a Repair Install.
    Repair Install Windows 10 with an In-place Upgrade
      My Computer


  3. Posts : 9
    Windows 10 Pro
    Thread Starter
       #3

    davidhk said:
    Suggestions :

    #1. do a system file check to look for corrupt files. If any found, it will try to do repair.
    Right click at Start button > click Command Prompt (Admin) > at the flashing prompt, copy/paste this.......
    sfc /scannow

    > press Enter.
    It will take quite sometime.
    When finished, it will give you one of the 3 reports...............(paraphrasing)
    1. No integrity violation.
    2. Found corrupt files and repair successful.
    3. Found corrupt files but unable to repair.


    If you have report #3. Please post back. There is way to fix that.

    #2. If suggestion #1 does not help, do a Repair Install.
    Repair Install Windows 10 with an In-place Upgrade

    So it didn't quite work as expected? See below:

    Beginning verification phase of system scan.
    Verification 100% complete.


    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.


    C:\WINDOWS\system32>


    Here's part of that log towards the end:

    2016-03-18 09:32:47, Info CSI 0000555a@2016/3/18:13:32:47.564 Primitive installers committed for repair
    2016-03-18 09:32:47, Info CSI 0000555b [SR] Verify complete
    2016-03-18 09:32:47, Info CSI 0000555c [SR] Repairing 1 components
    2016-03-18 09:32:47, Info CSI 0000555d [SR] Beginning Verify and Repair transaction
    2016-03-18 09:32:47, Info CSI 0000555e Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-03-18 09:32:47, Info CSI 0000555f [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-03-18 09:32:47, Info CSI 00005560@2016/3/18:13:32:47.583 Primitive installers committed for repair
    2016-03-18 09:32:47, Info CSI 00005561 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-03-18 09:32:47, Info CSI 00005562 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-03-18 09:32:47, Info CSI 00005563 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
    2016-03-18 09:32:47, Info CSI 00005564 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-03-18 09:32:47, Info CSI 00005565 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
    Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
    2016-03-18 09:32:47, Info CSI 00005566 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2016-03-18 09:32:47, Info CSI 00005567@2016/3/18:13:32:47.643 Primitive installers committed for repair
    2016-03-18 09:32:47, Info CSI 00005568 [SR] Repair complete
    2016-03-18 09:32:47, Info CSI 00005569 [SR] Committing transaction
    2016-03-18 09:32:47, Info CSI 0000556a Creating NT transaction (seq 2), objectname [6]"(null)"
    2016-03-18 09:32:47, Info CSI 0000556b Created NT transaction (seq 2) result 0x00000000, handle @0x12f4
    2016-03-18 09:32:47, Info CSI 0000556c@2016/3/18:13:32:47.716 Beginning NT transaction commit...
    2016-03-18 09:32:47, Info CSI 0000556d@2016/3/18:13:32:47.766 CSI perf trace:
    CSIPERF:TXCOMMIT;56437
    2016-03-18 09:32:47, Info CSI 0000556e [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
    2016-03-18 09:34:48, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2016-03-18 09:34:48, Info CBS TiWorker signaled for shutdown, going to exit.
      My Computer


  4. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #4

    RE : found corrupt files but unable to repair

    In the same Command Prompt (Admin) windows, copy and paste this command...........

    dism /online /cleanup-image /restorehealth

    > press Enter.
    Again it will take some time.
    When finished, it will give you a report.

    If you receive the report that " Source files could not be found " please post back.
    There is also a way to fix that.
      My Computer


  5. Posts : 9
    Windows 10 Pro
    Thread Starter
       #5

    davidhk said:
    RE : found corrupt files but unable to repair

    In the same Command Prompt (Admin) windows, copy and paste this command...........

    dism /online /cleanup-image /restorehealth

    > press Enter.
    Again it will take some time.
    When finished, it will give you a report.

    If you receive the report that " Source files could not be found " please post back.
    There is also a way to fix that.
    Got the source files could not be found:

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================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 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
      My Computer


  6. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #6

    OK.
    Use the Tech Bench link and download the corresponding ISO file.
    http://www.microsoft.com/en-us/softw...load/techbench

    Make sure you select Windows 10 ( first one on the list ).
    Make sure you select the same language as your computer is now using.
    Same applies to bit version.

    Once you have the iso downloaded, right click at the ISO > click Mount > and leave it there.
    Now open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
      My Computer


  7. Posts : 9
    Windows 10 Pro
    Thread Starter
       #7

    davidhk said:
    OK.
    Use the Tech Bench link and download the corresponding ISO file.
    http://www.microsoft.com/en-us/softw...load/techbench

    Make sure you select Windows 10 ( first one on the list ).
    Make sure you select the same language as your computer is now using.
    Same applies to bit version.

    Once you have the iso downloaded, right click at the ISO > click Mount > and leave it there.
    Now open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
    Thanks for the help. I am downloading the iso now. It's WIN10_1511_1_English_x64.iso. It's telling me that it will take 3 hours to download but it keeps jumping around. I have been downloading it for a half hour or so. I will post an update later on today.
      My Computer


  8. Posts : 19,516
    W11+W11 Developer Insider + Linux
       #8

    I had same problem and only shutting Firewall down helped.
      My Computers


  9. Posts : 9
    Windows 10 Pro
    Thread Starter
       #9

    CountMike said:
    I had same problem and only shutting Firewall down helped.
    No luck with that. Thanks for the suggestion, though.
      My Computer


  10. Posts : 9
    Windows 10 Pro
    Thread Starter
       #10

    davidhk said:
    OK.
    Use the Tech Bench link and download the corresponding ISO file.
    http://www.microsoft.com/en-us/softw...load/techbench

    Make sure you select Windows 10 ( first one on the list ).
    Make sure you select the same language as your computer is now using.
    Same applies to bit version.

    Once you have the iso downloaded, right click at the ISO > click Mount > and leave it there.
    Now open the elevated command prompt and copy and paste this................

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:H:\sources\install.wim:1 /limitaccess

    Note : H is the drive where the iso is mounted. Change it if your driver letter is different.

    When it is completed, you should get the report that the operation is successful.
    Now run the sfc /scannow again. It should be ok this time.
    So I did this and it did not work for me. The tiles are still auto closing and I can't install anything in the store.

    C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:\sources\install.wim:1 /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================100.0%==========================]
    The restore operation completed successfully.
    The operation completed successfully.


    C:\WINDOWS\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files and successfully repaired
    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.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:44.
Find Us




Windows 10 Forums