Windows Insider 17733 – How do I get off this build?

Solution: Run windows update via Command line wuauclt.exe /updatenow

Several of the most recent Windows Insider builds have had issues.  Mainly performance delays of an hour.  How did this miss Canary… but here we are.  Good news the 17735 build came out that looks to address the overlay issue of Settings.    Why is this important?  Well you can’t get off this bad build until you run windows update.  However, one of the bugs is the inability to run Windows update.  Catch-22?

Thankfully, NO!

Command line to the rescue. If you are running a windows 10 tablet without a keyboard here is your method.  You can skip several of these steps if you have a keyboard.

  1. Click and hold the start key (equivalent of Windows Key + X or right click)
  2. Select Windows PowerShell (Admin)
  3. If you are on 17733 you might have to come back to the device in 60 minutes before you are prompted for UAC
  4. Once in PowerShell you can type CMD
  5. This will open a command prompt in C:\windows\system32
  6. Type in and execute wuauclt.exe /updatenow
  7. Wait
  8. Check start >> Reboot to see it you have a Update and Restart option
    1. If you don’t just wait or type in the keyboard command again



Windows Store Install Error 0x803F8001

While playing around with the most recent Windows Insider build I ran into an application that was receiving the 0x803F8001 Error.  Ironically, I have not been able to find exact error code in online documentation.  Instead I am going to write a short summary of methods to work with the Windows Store to resolve a multitude of issues including this one.


Windows EventViewer Error Details

Fault bucket , type 0
Event Name: StoreAgentAcquireLicenseFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Update;Microsoft.WindowsStore_8wekyb3d8bbwe
P2: 803f8001
P3: 14393
P4: 576
P5: Windows.Desktop
P6: N

Attached files:

These files may be available here:

Analysis symbol: 
Rechecking for solution: 0
Report Id: 73e2874a-d67b-11e6-9ae3-e4b318276f42
Report Status: 4100
Hashed bucket:

Ahh, StoreAgentAcquireLicenseFailure1.  Access denied or Corrupt files.  Interesting.  Lets dig further!

Windows Store TroubleShooter 

No Joy but it did do things… what are those things?

Reset the Windows Store

  1. Open Administrator Command Prompt
    1. Winkey + X
    2. Command Prompt (Admin)
  2. WSReset.exe
    1. Resets the Windows Store (will close and reopen the Windows Store)

No Joy but now I feel better!

Register the Catalog Manifest again

Run the following from a Admin Command Prompt (see above on how to open one)

PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.Windows
Store).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

Just a note, this won’t work if the store is open.  So close the store 🙂

Error if Store is Open

Add-AppxPackage : Deployment failed with HRESULT: 0x80073D02, The package could not be installed because resources it
modifies are currently in use.
error 0x80004004: Unable to install because the following apps need to be closed
NOTE: For additional information, look for [ActivityId] 35681ba7-696a-0003-86d6-69356a69d201 in the Event Log or use
the command line Get-AppxLog -ActivityID 35681ba7-696a-0003-86d6-69356a69d201
At line:1 char:97
+ ... fest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manife ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : NotSpecified: (C:\Program File...ppxManifest.xml:String) [Add-AppxPackage], Exception
 + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Ironically the steps above did not resolve the issue in question.  What did?

Fix: Uninstall and Reinstall

Uninstall the app from the start menu.  By right click and uninstall


Open the store and go shop for the app again.

Be aware, this was a minor application but an app with lots of configuration files will all be reset to default.

So what is actually broken?

This leads me to believe there is a corrupted install somewhere in your local user profile.


That means it is either a stuck transfer via BITS or Corrupted access on the local device.  Why am I leaning towards access?  Because the app still opens and runs fine but I cannot update it.

I am going to keep looking for a direct definition of the error code and the access denied issue