Skip to content

Fix broken forum links in developer mode documentation #5540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 29, 2025
Merged

Conversation

Copilot
Copy link
Contributor

@Copilot Copilot AI commented Jul 29, 2025

The developer mode documentation contained broken links to the old MSDN "Known Issues forum" that no longer exists and redirects to the Learn landing page. These links were causing users to be unable to find support for Developer Mode and Device Portal issues.

Changes made:

  • Replaced broken forum links with references to the existing Feedback Hub mechanism already documented in the same file
  • Updated the Device Portal troubleshooting section to direct users to the "Failure to install Developer Mode package" section and Feedback Hub
  • Streamlined the "Failure to install Developer Mode package" section to directly encourage using the Feedback Hub app
  • Fixed markdown formatting for the NOTE block containing Feedback Hub instructions

Before:

See the [Known Issues forum](https://social.msdn.microsoft.com/Forums/en-US/home?forum=Win10SDKToolsIssues&sort=relevancedesc&brandIgnore=True&searchTerm=%22device+portal%22) to find workarounds for these issues (and others).

After:

If Developer Mode doesn't install correctly, we encourage you to file a feedback request using the Feedback Hub app.

This solution leverages the existing, well-documented Feedback Hub mechanism that's already detailed in the document, providing users with a working path to report issues and get support.

Fixes #5019.


💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

Copy link
Contributor

Learn Build status updates of commit 9427547:

⚠️ Validation status: warnings

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@mattwojo
Copy link
Contributor

@copilot - Remove the text and link to the Known issues forum identified in this issue, as that forum is no longer available.

@Copilot Copilot AI changed the title [WIP] Bad link to "Known Issues forum" Fix broken forum links in developer mode documentation Jul 29, 2025
@Copilot Copilot AI requested a review from mattwojo July 29, 2025 21:14
Copilot finished work on behalf of mattwojo July 29, 2025 21:14
Copy link
Contributor

Learn Build status updates of commit 9b7b5de:

✅ Validation status: passed

File Status Preview URL Details
hub/apps/get-started/developer-mode-features-and-debugging.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor Author

Copilot AI commented Jul 29, 2025

@copilot - Remove the text and link to the Known issues forum identified in this issue, as that forum is no longer available.

I have already removed all references to the "Known Issues forum" and the broken MSDN links from the developer mode documentation. Both instances have been replaced with references to the Feedback Hub mechanism. The changes are in commit 9b7b5de.

Copy link
Contributor

Learn Build status updates of commit 9b7b5de:

✅ Validation status: passed

File Status Preview URL Details
hub/apps/get-started/developer-mode-features-and-debugging.md ✅Succeeded

For more details, please refer to the build report.

Copilot finished work on behalf of mattwojo July 29, 2025 21:17
@mattwojo mattwojo marked this pull request as ready for review July 29, 2025 21:23
@mattwojo mattwojo merged commit 5261ce4 into docs Jul 29, 2025
3 checks passed
@mattwojo mattwojo deleted the copilot/fix-5019 branch July 29, 2025 21:31
leahyra pushed a commit to leahyra/windows-dev-docs that referenced this pull request Aug 13, 2025
…0309158086sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bad link to "Known Issues forum"
2 participants