Announcing Windows 10 Insider Preview Fast Build 17110 - Feb. 27 Insider

Page 12 of 15 FirstFirst ... 21011121314 ... LastLast

  1. Posts : 68,987
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #110

    ***STORE WORKAROUND***

    If you are hitting this issue, please do the following:

    1. Reboot your device
    2. Open Powershell (with Admin permissions)
    3. Paste in the following command:

    Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
    4. Reboot the device
    5. Store should now work
      My Computers


  2. Posts : 504
    Win10 20236.1000 64bit Pro and Win7 SP1 Ultimate
       #111

    Store in 17110


    I used Chris' fix for the Store and it worked just fine without a reboot.

    Thanks much, Chris.

    WEK
      My Computers


  3. Posts : 336
    Win 10 Pro x64 21H1 19043.964
       #112

    Brink said:
    ***STORE WORKAROUND***

    If you are hitting this issue, please do the following:

    1. Reboot your device
    2. Open Powershell (with Admin permissions)
    3. Paste in the following command:

    Get-AppXPackage *WindowsStore* -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
    4. Reboot the device
    5. Store should now work




    Thank you Brink, I had to reboot to get it to work, just thought I'd add that.
      My Computers


  4. Posts : 1,490
    Windows 10 Pro x64-bit Build Latest
       #113

    cbwilsha said:
    Please put it in Feedback Hub. I already have for both 17107 and 17110.
    I will do that!

    But I will be reverting to build 17101, I need this working as it should because sometimes I am off office and needing to access the computer remotely and when I try to wake it up it crashes instead.
      My Computer


  5. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #114

    cbwilsha said:
    "No, turning Hibernate back on worked for me ... powercfg -h on and then going into Settings and manually turning off (unchecking) Hibernate and Fast Startup (leaving Sleep checked). "


    Wynona, I tried that again several times but it still didn't work for me. Am I correct in assuming you had to do that in 17110 also to get sleep wake to work?
    No, once I got it to work in Build 17107, it worked in the 17110 update.
      My Computer


  6. Posts : 1,481
    W10 22H2 19045.3031
       #115

    Late in updating, don't like what gets installed at the same time?? NVIDA?? Its taking it's sweet old time.
    Attached Thumbnails Attached Thumbnails Announcing Windows 10 Insider Preview Fast Build 17110 - Feb. 27-17110.jpg  
      My Computers


  7. Posts : 1,481
    W10 22H2 19045.3031
       #116

    Installed and image made. The powercfg file remained OFF, and I did several restarts, sleeps etc and it works as normal. Did the Store work around and the store icon re-appeared. This one took about 2 hrs to finish which is unusual for me, average has been a little over an hour.
      My Computers


  8. Posts : 1,937
    win 10 Insider
       #117

    After fixing Store, all good now.
      My Computers


  9. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #118

    Now when we have the Store issue solved, I just realized an issue about PowerShell (in general).

    Here are the inputs and outputs I am looking at:

    Test 1
    Code:
    Input 1
    foreach ($location in (Get-AppxPackage *WindowsStore* -AllUsers).InstallLocation) {Write-Host $location\AppXManifest.xml}
    
    Output 1
    C:\Program Files\WindowsApps\Microsoft.WindowsStore_11802.1001.3.0_x64__8wekyb3d8bbwe\AppXManifest.xml
    Test 2
    Code:
    Input 2
    foreach ($location in (Get-AppxPackage *WindowsStore* -AllUsers)) {Write-Host $location.InstallLocation\AppXManifest.xml}
    
    Output 2
    C:\Program Files\WindowsApps\Microsoft.WindowsStore_11802.1001.3.0_x64__8wekyb3d8bbwe \AppXManifest.xml
    Test 3
    Code:
    Input 3
    foreach ($location in (Get-AppxPackage *WindowsStore* -AllUsers)) {Write-Host "$($location.InstallLocation)\AppXManifest.xml"}
    
    Output 3
    C:\Program Files\WindowsApps\Microsoft.WindowsStore_11802.1001.3.0_x64__8wekyb3d8bbwe\AppXManifest.xml
    Why do I get an extra space in example 2? Only thing I did was, I moved the .InstallLocation to be extracted from $location variable instead of straight from the first command. Why does adding "$(blah blah)" solve this issue? What is that extra character? it certainly is NOT a space/whitespace since .Trim() does nothing to it.

    No wonder .Net and PS produce errors if one has to deal with such weird behavior.
      My Computers


  10. Posts : 2,161
    Windows 11 Beta channel
       #119

    I had to roll back to 17107. With 17110 and the newest Nvidia drivers, if I tried to open Chrome while also gaming I'd get a massive memory leak, resulting in the whole system locking up. After rolling back to 17107, that issue has gone away.
      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 17:59.
Find Us




Windows 10 Forums