You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/advanced-settings/developer-mode.md
+107-1Lines changed: 107 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,9 @@ When you enable Developer Mode on desktop, a package of features is installed, i
58
58
59
59
### Device Portal
60
60
61
-
To learn more about Device Portal, see [Windows Device Portal overview](/windows/uwp/debug-test-perf/device-portal) and [Device Portal for desktop](/windows/uwp/debug-test-perf/device-portal-desktop).
61
+
To learn more about Device Portal, see [Windows Device Portal overview](/windows/uwp/debug-test-perf/device-portal).
62
+
63
+
For specific setup instructions, see [Device Portal for desktop](/windows/uwp/debug-test-perf/device-portal-desktop).
62
64
63
65
### Device Discovery
64
66
@@ -82,3 +84,107 @@ SSH login is done via the *DevToolsUser* account, which accepts a password for a
82
84
##### Caveats for SSH usage
83
85
84
86
The existing SSH server used in Windows is not yet protocol compliant. Using an SFTP or SSH client may require special configuration. In particular, the SFTP subsystem runs at version 3 or less, so any connecting client should be configured to expect an old server. The SSH server on older devices uses `ssh-dss` for public key authentication (which OpenSSH has deprecated). To connect to such devices, the SSH client must be manually configured to accept `ssh-dss`.
87
+
88
+
## Failure to install Developer Mode package
89
+
90
+
Sometimes, due to network or administrative issues, Developer Mode won't install correctly. The Developer Mode package is required for remote deployment to this PC (using Device Portal from a browser or Device Discovery to enable SSH), but not for local development. Even if you encounter these issues, you can still deploy your app locally using Visual Studio (or from this device to another device).
91
+
92
+
If Developer Mode doesn't install correctly, we encourage you to file a feedback request using the Feedback Hub app.
93
+
94
+
> [!NOTE]
95
+
> 1. Install the [Feedback Hub app](https://apps.microsoft.com/store/detail/feedback-hub/9NBLGGH4R32N) (if you don't already have it) and open it.
96
+
> 2. Click **Add new feedback**.
97
+
> 3. Choose the **Developer Platform** category and the **Developer Mode** subcategory.
98
+
> 4. Fill out the fields (you may optionally attach a screenshot) and click **Submit**.
99
+
>
100
+
> Submitting feedback will help Microsoft resolve the issue you encountered.
101
+
102
+
### Failed to locate the package
103
+
104
+
> Developer Mode package couldn't be located in Windows Update. Error Code 0x80004005. Learn more.
105
+
106
+
This error may occur due to a network connectivity problem, Enterprise settings, or the package may be missing.
107
+
108
+
To fix this issue:
109
+
110
+
1. Ensure that your computer is connected to the internet.
111
+
2. If you're on a domain-joined computer, speak to your network administrator. The Developer Mode package (like all Features on Demand) is blocked by default in WSUS 2.1. In order to unblock the Developer Mode package in the current and previous releases, the following KBs should be allowed in WSUS:
112
+
113
+
- 4016509
114
+
- 3180030
115
+
- 3197985
116
+
117
+
3. Check for Windows updates in **Settings → Updates and Security → Windows Updates**.
118
+
1. Verify that the Windows Developer Mode package is present in **Settings → System → Optional features → Add a feature** (on versions older than Windows 10 22H2, look under **Settings****→****Apps****→****Apps & features****→ Optional features****→****Add a feature**). If it's missing, Windows can't find the correct package for your computer.
119
+
120
+
5. After performing the above steps, *disable* and then *re-enable* Developer Mode to verify the fix.
121
+
122
+
### Failed to install the package
123
+
124
+
> Developer Mode package failed to install. Error code 0x80004005. Learn more.
125
+
126
+
This error may occur due to incompatibilities between your build of Windows and the Developer Mode package.
127
+
128
+
To fix this issue:
129
+
130
+
1. Check for Windows updates in the **Settings → Updates and Security → Windows Updates**.
131
+
2. Restart your computer to ensure all updates are applied.
132
+
133
+
## Use group policies or registry keys to enable a device
134
+
135
+
For most developers, you'll want to use Windows Settings to enable your device for debugging. In certain scenarios (such as automated tests) you can use other ways to enable your Windows desktop device for development.
136
+
137
+
> [!NOTE]
138
+
> These steps will not enable the SSH server or allow the device to be targeted for remote deployment and debugging.
139
+
140
+
You can use `gpedit.msc` to set the group policies to enable your device, unless you have *Windows 10 Home* or *Windows 11 Home*. If you do, you'll need to use regedit or PowerShell commands to set the registry keys directly to enable your device.
141
+
142
+
### Use gpedit to enable your device
143
+
144
+
1. Run `gpedit.msc`.
145
+
146
+
2. Go to **Local Computer Policy → Computer Configuration → Administrative Templates → Windows Components → App Package Deployment**.
147
+
148
+
3. Edit the following policies to enable sideloading:
149
+
150
+
- Allow all trusted apps to install.
151
+
152
+
OR
153
+
154
+
Edit the following policies to enable both sideloading and Developer Mode:
155
+
156
+
- Allow all trusted apps to install.
157
+
- Allows development of UWP apps and installation from an *Integrated Development Environment (IDE)*.
158
+
- Reboot your machine.
159
+
160
+
### Use regedit to enable your device
161
+
162
+
1. Run `regedit`.
163
+
164
+
2. To enable sideloading, set the value of this `DWORD` to `1`:
Copy file name to clipboardExpand all lines: hub/apps/develop/search/search-providers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Windows Search currently uses the Web Search from Microsoft Bing app to return w
14
14
15
15
Search providers integrate with the Search experience by creating an [MSIX package](/windows/msix/) with a package manifest file that provides the required information for the OS to register the search provider. After installation, the search provider is enabled by default in Windows Search experiences. In Windows Settings, users can enable and disable installed search providers and manage the order of providers in search results. Users can remove a search provider through the **Settings > Apps > Installed apps** page in Windows Settings.
16
16
17
-
For development and testing, when Developer Mode is enabled and the search provider app has been sideloaded on the device, it will appear in the list of available search providers. For more information, see [Developer Mode features and debugging](/windows/apps/get-started/developer-mode-features-and-debugging).
17
+
For development and testing, when Developer Mode is enabled and the search provider app has been sideloaded on the device, it will appear in the list of available search providers. For more information, see [Settings for developers](/windows/advanced-settings/developer-mode).
18
18
19
19
Once the search provider is registered with the OS, user queries are passed to the HTTP endpoint specified by the provider in their package manifest using a standardized query string. The endpoint returns suggested results in a JSON document. With each suggested URL in the response document, the search provider includes the preview endpoint URL, which returns an HTML document that is displayed in the preview pane in the search results UI.
0 commit comments