Microsoft has acknowledged that Windows 10 version 1803 can “hang or freeze” while running certain applications and will fix the issue.
“Microsoft is aware that some devices running the Windows 10 April 2018 Update (version 1803) may hang or freeze when using certain apps, such as ‘Hey Cortana’ or Chrome,” a Microsoft support document explains. “Microsoft is working on a solution with the goal of including it in the next regular monthly update, currently targeted for a release date of May 8, 2018.”
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
I’m guessing a lot more people noticed this while using Chrome than “Hey Cortana,” but whatever. That Windows 10 version 1803 shipped with this kind of obvious bug in the wake of a serious reliability problem that caused Microsoft to delay this release by weeks says a lot about how things are going in Redmond these days. And it’s not positive.
In the meantime, Microsoft offers the following workaround if you are experiencing freezes or hangs:
This is alarming.
skane2600
<blockquote><a href="#271541"><em>In reply to fbman:</em></a></blockquote><p>Yes, the ease and low cost of updates has made companies lazy and complacent. In earlier times a software bug would require new floppies be sent to the customer or in the case of an embedded product, a product return or service call. Doing it right the first time was taken seriously in those days.</p><p><br></p><p>I don't buy the increased complexity excuse either. The hardware resources and development tools are far superior to what we used to have. Of course when you mix and match a bunch of different Open Source libraries you haven't tested, you going to encounter some surprises.</p>
jumpingjackflash5
<p>Windows should really focus on stability, reliability and preserving users' settings including configuration of drivers during updates. Make just one annual feature update with voluntary install. Provide security updates that do not change the compatibility. What happens after every major update mustn't happen with dependable and mature operating system. Which Windows is supposed to be. Operating system. Not a service.</p>
skane2600
<blockquote><a href="#269488"><em>In reply to bluvg:</em></a></blockquote><p>I think it's just evidence that unit testing alone is an inadequate QA methodology. Of course developers were testing their code long before unit testing became a religion.</p>
skane2600
<blockquote><a href="#271695"><em>In reply to Waethorn:</em></a></blockquote><p>Sometimes it can, but yes, not always. IMO, it's less about objectivity and more about the inability of unit tests alone to determine whether the requirements are met. </p>
skane2600
<blockquote><a href="#271823"><em>In reply to Waethorn:</em></a></blockquote><p>The important question is whether a developer can EVER determine that their own code is correct at the same level of competence as a third party and of course the answer is "yes". Whether that scenario meets any particular definition of an "objective review" is a different question. Is it a good idea to avoid a third party review, no, but that doesn't mean that a developer's own testing can't be valid.</p>
Stooks
<p>This and all version in the past remove the RSAT tools. You then have to go find the latest version and install them, reset your preferences etc.</p><p><br></p><p>The sheer amount of things I need to remove after a clean install is almost as bad as the sheer amount of updates there are for a fresh install of Windows 7. I used to powershell remove all of this stuff, but I would constantly be updating the powershell scripts to get it done. Now I just download cleaner, go to the tools section, click uninstall 20 or more times to get Windows 10 back to the point I want.</p><p><br></p><p>Windows 10 is such a mess. LTSB…oh wait they changed the name for the heck of it…LTSC is the very best way to use Windows 10. To bad consumers can't get access too it.</p>
skane2600
<blockquote><a href="#271095"><em>In reply to hrlngrv:</em></a></blockquote><p>Rolling layoffs are the worst for morale and indicate that management doesn't have their s**t together. Figure out your plan for the next few years and execute it. A company like MS could keep their current employee count for years and still remain profitable anyway. </p>
skane2600
<blockquote><a href="#271699"><em>In reply to davidblouin:</em></a></blockquote><p>This is a Microsoft product, so of course they deserve 100% of the blame or the praise. </p>
skane2600
<blockquote><a href="#271796"><em>In reply to davidblouin:</em></a></blockquote><p>Insiders are unpaid people that have no ethical or legal obligation to perform any QA work and even if they were paid, they'd simply be part of Microsoft. There's a long history of beta testers but they've never been considered responsible for the errors in a company's code. The common literary disclaimer is instructive: "Any errors, deficiencies, or problems in this book are my own".</p>
skane2600
<blockquote><a href="#271978"><em>In reply to davidblouin:</em></a></blockquote><p>You can blame them if you want. </p>