Skip to content

Windows

Corrupted UI or strange colors

Ensure you are running the latest driver for your graphics adapter.

Port 49734 is unavailable, but Windows say it's not in use?

On Windows a port may be reserved, even if it is not in use. https://stackoverflow.com/questions/54010365/how-to-see-what-is-reserving-ephemeral-port-ranges-on-windows

See reserved ports using this command: 

netsh int ipv4 show excludedportrange protocol=tcp

A possible fix is to run the commands below. This might cause you to lose internet connection until rebooting. It should free up reserved ports and add the Foldersync Desktop port to the excluded range so it will no longer be reserved by winnat. 

net stop winnat
net start winnat
netsh int ipv4 add excludedportrange protocol=tcp startport=49734 numberofports=1

I get error 0x80070422 or similar when trying to install MSIX version?

The error code 0x80070422 maps to ERROR_SERVICE_DISABLED. When users run into this while installing an MSIX application, it almost always means that a critical background Windows service—usually the Windows Update service or a closely related deployment service—has been disabled. Because MSIX packages rely heavily on the OS deployment engine (AppX Deployment Service) and frequently ping the Windows Update infrastructure for core infrastructure dependencies, a disabled service halts the entire installation. Here is the exact step-by-step checklist you can share with your users to resolve this:

Step 1: Enable Crucial Windows Services

Have the user check that the essential components required for package extraction and installation are enabled.

  1. Press Win + R, type services.msc, and press Enter.
  2. Locate the Windows Update service.
  3. Right-click it and select Properties.
  4. Change the Startup type to Manual or Automatic.
  5. If the service status is stopped, click Start, then click Apply and OK.

Note: While they are in the Services window, ensure they also check that the Background Intelligent Transfer Service (BITS) and the AppX Deployment Service (AppXSvc) are not explicitly disabled.

Step 2: Try installing via PowerShell (As Administrator)

If the graphical App Installer is still being stubborn, running the installation directly through an elevated PowerShell window usually bypasses UI hang-ups and provides clearer debug feedback.

  1. Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
  2. Run the following command (replacing the path with the actual file location):

Add-AppxPackage -Path "C:\Path\To\YourApp.msix"

If it fails here, it will give an explicit, precise error tracking component instead of a generic UI code.

Step 3: Run the Windows Store Apps Troubleshooter

Sometimes a underlying system policy glitch locks the deployment engine. Windows has a built-in repair tool for this. • On Windows 11: Go to Settings > System > Troubleshoot > Other troubleshooters and run the Windows Store Apps troubleshooter. • On Windows 10: Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters and select Windows Store Apps.

Step 4: Repair Corrupted System Files

If the service refuses to start or errors out instantly, system file degradation might be blocking it.

  1. Open PowerShell (Admin).
  2. Run this command to repair the component store image: DISM.exe /Online /Cleanup-image /Restorehealth
  3. Once finished, run the system file checker: sfc /scannow
  4. Restart the PC and attempt the installation again.

Are your users downloading this MSIX over the web via an .appinstaller file, or are they installing a local package directly from their drive?