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/design/accessibility/high-contrast-themes.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
@@ -69,7 +69,7 @@ A [**ResourceDictionary.ThemeDictionaries**](/uwp/api/windows.ui.xaml.resourcedi
69
69
70
70
## Contrast colors
71
71
72
-
On the *Settings > Ease of access > Contrast themes* page (shown in the following image), users can select from four default contrast themes: **Aquatic**, **Desert**, **Dusk**, and **Night sky**.
72
+
On the *Settings > Accessibility > Contrast themes* page (shown in the following image), users can select from four default contrast themes: **Aquatic**, **Desert**, **Dusk**, and **Night sky**.
Copy file name to clipboardExpand all lines: hub/apps/design/basics/navigation-basics.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Don't overwhelm users with many navigation options.
77
77
78
78
Clear paths allow for logical navigation for users. Making navigation options obvious and clarifying relationships between pages should prevent users from getting lost.
79
79
80
-

80
+

81
81
82
82
> *Destinations are clearly labeled so users know where they are.*
83
83
@@ -86,7 +86,7 @@ Clear paths allow for logical navigation for users. Making navigation options ob
86
86
Now, let's take our design principles--consistency, simplicity, and clarity--and use them to come up with some general recommendations.
87
87
88
88
- Think about your users. Trace out typical paths they might take through your app, and for each page, think about why the user is there and where they might want to go.
89
-
- Avoid deep navigation hierarchies. If you go beyond two levels of navigation, provide a [breadcrumb bar](../controls/breadcrumbbar.md) that shows the user where they are and let's them quickly get back out. Otherwise, you risk stranding your user in a deep hierarchy that they will have difficulty leaving.
89
+
- Avoid deep navigation hierarchies. If you go beyond two levels of navigation, provide a [breadcrumb bar](../controls/breadcrumbbar.md) that shows the user where they are and lets them quickly get back out. Otherwise, you risk stranding your user in a deep hierarchy that they will have difficulty leaving.
90
90
- Avoid "pogo-sticking." Pogo-sticking occurs when there is related content, but navigating to it requires the user to go up a level and then down again.
91
91
92
92
## Use the right structure
@@ -204,7 +204,7 @@ Use tabs when:
204
204
:::column span="2":::
205
205
[**Breadcrumb**](../controls/breadcrumbbar.md)
206
206
207
-
Displays a horizontal list of links to pages at each of the higher levels. The [BreadcrumbBar](../controls/breadcrumbbar.md) control implements the top navigation pattern.
207
+
Displays a horizontal list of links to pages at each of the higher levels. The [BreadcrumbBar](../controls/breadcrumbbar.md) control implements the breadcrumb navigation pattern.
208
208
209
209
Use a breadcrumb when:
210
210
@@ -303,7 +303,7 @@ If you choose to provide your own back stack navigation, the experience should b
303
303
<p>The app displays content for an on-screen item, such as the details for the selected item in list/details list.</p></td>
304
304
<td><strong>No</strong>
305
305
<p>Enumerating items is similar to navigating within a peer group. When the user presses back, navigate to the page that preceded the current page that has the item enumeration.</p>
Copy file name to clipboardExpand all lines: hub/apps/design/basics/titlebar-design.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This section describes the design recommendations and behaviors of the parts of
25
25
- The standard title bar has a height of 32px.
26
26
- The title bar's default background is [Mica](../style/mica.md), however we recommend that title bars blend with the rest of the window if possible.
27
27
- Title bars help users differentiate when a window is active and inactive. All title bar elements should be semi-transparent when the window is inactive.
28
-
- The title bar colors should adjust when users switch to [high contrast themes](../accessibility/high-contrast-themes.md), or between [light and dark modes](../style/color.md).
28
+
- The title bar colors should adjust when users switch to [high contrast themes](../accessibility/high-contrast-themes.md), or between [light and dark modes](../signature-experiences/color.md).
29
29
- For high contrast themes, apps should use the `SystemColors` class for determining proper UI element coloring to facilitate a superior high-contrast experience.
30
30
31
31
**Behavior**
@@ -62,7 +62,7 @@ This section describes the design recommendations and behaviors of the parts of
62
62
63
63
- A right-click/press-and-hold on the icon should show the system window menu.
64
64
- A double-click/tap should toggle between maximizing the window and restoring the window.
65
-
- The window title and other textual elements in the title bar should respond to [text-scaling](../input/text-scaling.md). This might require that the title bar grows in height.
65
+
- The window title and other textual elements in the title bar should respond to [text-scaling](../../develop/input/text-scaling.md). This might require that the title bar grows in height.
Copy file name to clipboardExpand all lines: hub/apps/design/globalizing/globalizing-portal.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,12 @@ Most localization teams use special tools to aid the process. For example, by re
54
54
|[Guidelines for globalization](guidelines-and-checklist-for-globalizing-your-app.md)| Design and develop your app in such a way that it functions appropriately on systems with different language and culture configurations. |
55
55
|[Understand user profile languages and app manifest languages](manage-language-and-region.md)| This topic defines the terms "user profile language list", "app manifest language list", and "app runtime language list". We'll be using these terms in this topic and other topics in this feature area, so it's important to know what they mean. |
56
56
|[Globalize your date/time/number formats](use-global-ready-formats.md)| Design your app to be global-ready by appropriately formatting dates, times, numbers, phone numbers, and currencies. You'll then be able later to adapt your app for additional cultures, regions, and languages in the global market. |
57
-
|[Use templates and patterns to format dates and times](use-patterns-to-format-dates-and-times.md)| Use classes in the [**Windows.Globalization.DateTimeFormatting**](/uwp/api/windows.globalization.datetimeformatting?branch=live) namespace with custom templates and patterns to display dates and times in exactly the format you wish. |
57
+
|[Use templates and patterns to format dates and times](use-patterns-to-format-dates-and-times.md)| Use classes in the [**Windows.Globalization.DateTimeFormatting**](/uwp/api/windows.globalization.datetimeformatting) namespace with custom templates and patterns to display dates and times in exactly the format you wish. |
58
58
|[Adjust layout and fonts, and support RTL](adjust-layout-and-fonts--and-support-rtl.md)| Design your app to support the layouts and fonts of multiple languages, including RTL (right-to-left) flow direction. |
59
-
|[NumeralSystem values](glob-numeralsystem-values.md)| This topic lists the values available to the **NumeralSystem** property of various classes in the [**Windows.Globalization**](/uwp/api/windows.globalization?branch=live) namespace. |
59
+
|[NumeralSystem values](glob-numeralsystem-values.md)| This topic lists the values available to the **NumeralSystem** property of various classes in the [**Windows.Globalization**](/uwp/api/windows.globalization) namespace. |
60
60
|[Make your app localizable](prepare-your-app-for-localization.md)| A localized app is one that can be localized to other markets, languages, or regions without uncovering any functional defects in the app. The most essential property of a localizable app is that its executable code has been cleanly separated from its localizable resources. |
61
61
|[International fonts](loc-international-fonts.md)| This topic lists the fonts available for Windows apps that are localized into languages other than U.S. English. |
62
62
|[Design your app for bidirectional text](design-for-bidi-text.md)| Design your app to provide bi-directional text support (BiDi) so that you can combine script from left-to-right and right-to-left writing systems. |
63
-
|[Use the Multilingual App Toolkit 4.0](use-mat.md)| The Multilingual App Toolkit (MAT) 4.0 integrates with Microsoft Visual Studio 2017 and later to provide Windows apps with translation support, translation file management, and editor tools. |
64
-
|[Multilingual App Toolkit 4.0 FAQ & troubleshooting](mat-faq-troubleshooting.yml)| This topic provides answers to frequently-asked questions and issues related to the Multilingual App Toolkit (MAT) 4.0. |
63
+
|[Multilingual App Toolkit (MAT) announcements](mat-announcements.md)| The Multilingual App Toolkit (MAT) reached end-of-support on October 15, 2025, and is no longer available for new installations. Existing users can continue to use it without loss of functionality. |
65
64
|[Use the UTF-8 code page](use-utf8-code-page.md)| UTF-8 is the universal code page for internationalization. |
66
65
|[Prepare your application for the Japanese era change](japanese-era-change.md)| Learn about the May 2019 Japanese era change and how to prepare your application. |
Copy file name to clipboardExpand all lines: hub/apps/design/layout/attached-layouts.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
@@ -292,7 +292,7 @@ The UI for the Xbox Activity Feed uses a repeating pattern where each line has a
292
292
The code below walks through what a custom virtualizing UI for the activity feed might be to illustrate the general approach you might take for a **data layout**.
293
293
294
294
> [!TIP]
295
-
> If you have the **WinUI 3 Gallery** app installed, click here to [open the app and see the ItemsRepeater in action](winui3gallery:/item/ItemsRepeater). Get the app from the [Microsoft Store](https://apps.microsoft.com/detail/9P3JFPWWDZRC) or get the source code on [GitHub](https://github.com/microsoft/WinUI-Gallery).
295
+
> If you have the **WinUI 3 Gallery** app installed, click here to [open the app and see the ItemsRepeater in action](winui3gallery://item/ItemsRepeater). Get the app from the [Microsoft Store](https://apps.microsoft.com/detail/9P3JFPWWDZRC) or get the source code on [GitHub](https://github.com/microsoft/WinUI-Gallery).
0 commit comments