Device Portal for Desktop

Device Portal lets you view diagnostic information and interact with your desktop over HTTP from a browser window. You can use Device Portal to do the following:

  • See and manipulate a list of running processes
  • Install, delete, launch, and terminate apps
  • Change Wi-Fi profiles, view signal strength, and see ipconfig
  • View live graphs of CPU, memory, I/O, network, and GPU usage
  • Collect process dumps
  • Collect ETW traces
  • Manipulate the isolated storage of sideloaded apps

Set up device portal on Windows Desktop

Turn on developer mode

Starting in Windows 10, Version 1607, some of the newer features for desktop are only available when developer mode is enabled. For information about how to enable developer mode, see Enable your device for development.


Sometimes, due to network or compatibility issues, developer mode won't install correctly on your device. See the relevant section of Enable your device for development for help troubleshooting these issues.

Turn on device portal

Enable Device Portal in the For developers section of Settings. When you enable it, you must also create a corresponding username and password. Do not use your Microsoft account or other Windows credentials.

Device Portal section of the Settings app

Once Device Portal is enabled, you will see web links at the bottom of the section. Take note of the port number appended to the end of the listed URLs: this number is randomly generated when Device Portal is enabled but should remain consistent between reboots of the desktop. If you'd like to set the port numbers manually so that they remain permanent, see Setting port numbers.

These links offer two ways to connect to Device Portal: over the local network (including VPN) or through the local host.

Connect to Device Portal

To connet through local host, open a browser window and enter the address shown here for the connection type you're using.

  • Localhost:<PORT> or http://localhost:<PORT>
  • Local Network: https://<IP address of the desktop>:<PORT>

HTTPS is required for authentication and secure communication.

If you are using Device Portal in a protected environment, like a test lab, in which you trust everyone on your local network, have no personal information on the device, and have unique requirements, you can disable the Authentication option. This enables unencrypted communication, and allows anyone with the IP address of your computer to connect to and control it.

Device Portal content on desktop

Device Portal on desktop provides the standard set of pages. For detailed descriptions of these, see Windows Device Portal overview.

  • Apps manager
  • File explorer
  • Running Processes
  • Performance
  • Debug
  • Event Tracing for Windows (ETW)
  • Performance tracing
  • Device manager
  • Networking
  • Crash data
  • Features
  • Mixed Reality
  • Streaming Install Debugger
  • Location
  • Scratch

More Device Portal options

Registry-based configuration for Device Portal

If you would like to select port numbers for Device Portal (such as 80 and 443), you can set the following regkeys:

  • Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WebManagement\Service
    • UseDynamicPorts: A required DWORD. Set this to 0 in order to retain the port numbers you've chosen.
    • HttpPort: A required DWORD. Contains the port number that Device Portal will listen for HTTP connections on.
    • HttpsPort: A required DWORD. Contains the port number that Device Portal will listen for HTTPS connections on.

Under the same regkey path, you can also turn off the authentication requirement:

  • UseDefaultAuthorizer - 0 for disabled, 1 for enabled.
    • This controls both the basic auth requirement for each connection and the redirect from HTTP to HTTPS.

Command line options for Device Portal

From an administrative command prompt, you can enable and configure parts of Device Portal. To see the latest set of commands supported on your build, you can run webmanagement /?

  • sc start webmanagement or sc stop webmanagement
    • Turn the service on or off. This still requires developer mode to be enabled.
  • -Credentials <username> <password>
    • Set a username and password for Device Portal. The username must conform to Basic Auth standards, so cannot contain a colon (:) and should be built out of standard ASCII characters e.g. [a-zA-Z0-9] as browsers do not parse the full character set in a standard way.
  • -DeleteSSL
    • This resets the SSL certificate cache used for HTTPS connections. If you encounter TLS connection errors that cannot be bypassed (as opposed to the expected certificate warning), this option may fix the problem for you.
  • -SetCert <pfxPath> <pfxPassword>
  • -Debug <various options for authentication, port selection, and tracing level>
    • Run a standalone version of Device Portal with a specific configuration and visible debug messages. This is most useful for building a packaged plugin.
    • See the MSDN Magazine article for details on how to run this as System to fully test your packaged plugin.