June 2016 Windows 10 Anniversary Update Bug Bash

Hello from the Windows Insider Engineering team!

We are excited to again include you, the Windows Insiders, in the June 2016 Windows 10 Anniversary Update Bug Bash. We are kicking off the Bug Bash internally today as well so we are starting on this together. Similar to the last Bug Bash, this week our teams are focused on filing feedback submissions & up-votes alongside Windows Insiders. We will again be reviewing incoming feedback from Windows Insiders and Microsoft engineers, prioritizing the problems being reported, and fixing bugs based on your feedback.

If you have been installing Insider builds along the way between the Bug Bash in April and last week’s release to the Fast ring, you’ve noticed the wide variety of feature introductions, OS changes, and application updates that have been delivered. Today's release of 14366 for PC and 14364 for Mobile continues this experience and is the Bug Bash Build. Your ongoing feedback, as we saw in April Bug Bash, has been vital in bug discovery as well as insights into what changes we can bring in to make Windows 10 an even greater experience for our Customers.

Given the overwhelming response to the variety and number of Quests delivered in the previous Bug Bash, we will once again be using this feature of the Feedback hub both with our internal Microsoft engineers and Windows Insiders to help highlight different areas of the product to give feedback on. The first set of Quests for the June Bug Bash are available here.

We will be cycling Quests over the next 4 days so that we can highlight different area to focus on each day. However we will be bringing all of them back over the weekend for more feedback. The end time for the June Bug Bash is June 19th, 11:59 PM PST.

Once again Quests will be marked with:

LIMITED TIME Quests:

Quests marked as “LIMITED TIME” will expire within 24hrs of being published so make sure you get to these before the time runs out and they’re replaced with new Quests.

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 PC.

We also want to take this opportunity to recognize Insiders for their contribution in the prior April 2016 Windows 10 Anniversary Update Bug Bash. For this you will see badges in Feedback Hub light up for recognizing your participation in the Bug Bash. We will be giving out another set of June Bug Bash participation badge as well post the June Bug Bash conclusion.

We have lots of opportunities for Windows Insiders to participate in this Windows 10 Anniversary Update Bug Bash. If you participated in April 2016 Windows 10 Anniversary Update Bug Bash, much of the following may look familiar, but please take a moment to review as a precursor to getting started:

PC/Phone Flighting:

To participate in this Bug Bash, you must be a registered Windows Insider. To register your MSA or check for prior registration, visit insider.windows.com.

If you are already running Windows 10 Insider Preview builds, you’ll need to be on the latest Fast ring build. If you’d like to participate in the Bug Bash on an additional device that is not currently flighting, review the following steps:

Feedback is important for making changes and improvements in Windows 10. This communication with users helps Microsoft gauge product satisfaction, build quality, and is instrumental in guiding conversations regarding what changes to make within the OS.

Receiving quality and actionable feedback is key in achieving these goals. When providing feedback, please take the following steps:

Check for existing feedback

Another user may have already shared the same feedback. If they have, please “upvote” the existing feedback to help prevent duplicate submissions

Add additional comments to existing feedback. This can help others by providing clarity to existing information or additional scenarios to review

Provide feedback items one item at a time

When sharing feedback, logs may be collected depending on the type of feedback being submitted and system settings. Providing one at a time ensures the correct information is received

Provide a clear and thorough description of the issue

When sharing additional details, it is important to provide as much clarity of the issue as possible

Include steps to reproduce the issue

Attach screenshots (if applicable)

Please use the “reproduce issue” option if available for the type of feedback being submitted

We will be sending updates daily with the new quests, so stay tuned to the Feedback Hub for news and information. If you have questions, please reach out to us via Twitter! Our handle is @WindowsInsider.

Thanks again for participating in the June Bug Bash and helping make the Windows 10 Anniversary Update even better!