Windows 10 Insiders November Bug Bash begins today

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Fresh off the release of Windows 10 Insider Preview Build 14959 for Mobile and PC, Microsoft has announced that the November Bug Bash is now officially underway. While Dona Sarkar has mentioned that the focus of the Bash is on Creating, 3D, Windows Ink, and Developers, every Windows Insider is now invited to participate and report the nastiest of the latest Windows 10 bugs directly to Microsoft.

Overall, the Bug Bash will run from now until November 13th 11:59 PM PST both internally at Microsoft, and with Windows Insiders. As has been the routine, Quests will be placed in the Windows 10 Feedback hub to point Windows Insiders in the right direction for finding bugs.

Available here, Quests will cycle, and all will be brought back over for the weekend for additional feedback before the conclusion of the Bug Bash. For the complete details on what to expect with the quests, check out  Michael Fortin, Corporate VP for Windows and Device Core Quality’s description of the Bug Bash below.

ADVANCED Quests:

  • Quests marked as “ADVANCED” are more technical and may require changing the system configuration on your device and require an understanding on how to revert the changes after the Quest is done. You should only perform Quests that you feel comfortable doing, if something goes wrong you’ll need to be able to troubleshoot how to get back to a good state on your device.

UPDATE Quests:

  • Quests marked as “Update” exercise Update paths from Windows 10 Anniversary Update to the November 2016 Windows 10 Bug Bash build

DEVELOPER Quests:

  • Quests marked as “Developer Quests” specifically are designed for Developers and may require coding.

As a reward for your hard work, badges will be distributed in the Feedback Hub at the conclusion of the Bug Bash. Let us know if you will be participating in this bug bash by dropping us a comment in the section below!