{"id":21247,"date":"2021-09-04T01:03:52","date_gmt":"2021-09-03T23:03:52","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=21247"},"modified":"2022-11-04T11:46:52","modified_gmt":"2022-11-04T10:46:52","slug":"windows-11-microsoft-macht-startmen-taskleite-mit-teams-promo-kaputt","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2021\/09\/04\/windows-11-microsoft-macht-startmen-taskleite-mit-teams-promo-kaputt\/","title":{"rendered":"Windows 11: Microsoft breaks start menu\/taskbar with teams promo"},"content":{"rendered":"

\"Windows\"[German<\/a>]Windows Insiders who are testing Windows 11 as a preview version got an unpleasant surprise a few hours ago. Neither the Start menu nor the taskbar worked. Microsoft hurried up with a \"we are investigating this\" message and there is a workaround. And in a beta, things can go wrong. But the background is interesting: A promo for Teams seems to have been the reason for the failure of these shell components.<\/p>\n

<\/p>\n

\"\" I haven't tested Insider Previews of Windows 10 or Windows 11 for quite some time. So I wasn't affected by the latest flaw in Windows 11. <\/p>\n

Did a new build went wrong?<\/h2>\n

On September 2, 2021, builds 22449<\/a> And 22000.176<\/a> of Windows 11 were released for Windows Insiders to test in the relevant beta and dev channels. <\/p>\n

\"Windows<\/a><\/p>\n

Shortly after the release of these Insider Preview builds, Microsoft was flooded with user messages that the Start menu and taskbar were no longer responsive and that the settings page could not be accessed. In the above tweet<\/a>, Microsoft states that they are investigating the problem and ask for patience.<\/p>\n

A fix is suggested<\/h2>\n

After a few hours, Microsoft announced in a tweet<\/a> that they had found a fix and added it to the relevant Insider Preview announcement articles (here<\/a> and here<\/a>). <\/p>\n

<\/a><\/p>\n

I've copied the instructions for the workaround here:<\/p>\n

\n

Step 1:<\/strong> Use CTRL-ALT-DEL and choose to open Task Manager. <\/p>\n

Step 2<\/strong>: Choose \"More details\" at the bottom of Task Manager to expand Task Manager. <\/p>\n

Step 3<\/strong>: Go to \"File\" and choose \"Run new task\". <\/p>\n

Step 4:<\/strong> Type \"cmd\" in the \"Open\" field. <\/p>\n

Step 5:<\/strong> Paste the following (everything in bold):
reg delete HKCU\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\IrisService \/f && shutdown -r -t 0<\/strong><\/p>\n

Step 6<\/strong>: Hit enter, and then your PC should reboot. After rebooting, everything should be back to normal.<\/p>\n<\/blockquote>\n

Thus, a registry entry has to be deleted and then restarted to cure the unresponsive taskbar or Start menu. Later, the Microsoft team added an explanation<\/a> after the bug had been fixed by a service-side correction.  <\/p>\n

Cause: Failed Teams promo<\/h2>\n

The interesting question now is what was the cause of this error, which led to the failure of the taskbar and Start menu, as well as other components. Microsoft is keeping a low profile in its blog posts and on Twitter. But one user provided the relevant clue to the background in this tweet<\/a>. It is related to the integration of Ads services for advertisements. <\/p>\n

\"Teams-Promo<\/p>\n

This blog post<\/a> contains the relevant clues. Microsoft sent out a promotional message to preview testers of Windows 11. The promotional message was supposed to advertise the upcoming operating system's integration with Microsoft Teams. Instead, the message caused Explorer (the Windows desktop shell) to become unresponsive and left users without a working Start menu and taskbar.<\/p>\n

The author of the blog post<\/a> was affected by this issue after restarting his laptop to complete the installation of another software. It was annoying and frustrating for the tester to be left with a broken Windows desktop.<\/p>\n

The sufferer then dug a little deeper and found that the problem was caused by a small file downloaded by a Windows component called IrisService. Iris is a part of Windows Spotlight (the Bing wallpaper of the day as well as tips, promotions and suggestions on the lock screen).<\/p>\n

Using the workaround provided by Microsoft, the tester was able to narrow down the problem to a registry key that contained a serialized JSON blob. The blob contained an advertisement for Microsoft Teams. The messages and images in the ad were identical to the window users see when they press the Windows key + C on a Windows account that is not yet set up with Teams. However, it's unclear if it's exactly that ad, the author of the blog post writes.<\/p>\n

And, he adds, there's a huge elephant in the room: how could Microsoft have let this happen? How can a single ad or JSON blog screw the shell when the associated service doesn't exist or is down. The author of the article fails to find an answer to the question of why the Windows shell was so poorly designed in the first place to become unresponsive because of a single failed cloud service? <\/p>\n

The user follows up by saying that advertising in Windows is important to Microsoft, but is not on the priority list for customers. Customers don't want advertising in Windows! Millions of people rely on Windows every day, and it simply has to be more robust than what is delivered with the Insider Preview. Bleeping Computer has given some more hints here<\/a>. <\/p>\n

Even though these are all still Previews, it's crystallizing that Microsoft doesn't really have a handle on the development processes there either. And on October 5, 2021, the product is supposed to be unleashed on the general public.<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]Windows Insiders who are testing Windows 11 as a preview version got an unpleasant surprise a few hours ago. Neither the Start menu nor the taskbar worked. Microsoft hurried up with a \"we are investigating this\" message and there is … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[47,2643],"class_list":["post-21247","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-issue","tag-windows-11"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/21247","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=21247"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/21247\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=21247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=21247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=21247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}