{"id":3448976,"date":"2026-01-26T08:59:51","date_gmt":"2026-01-26T06:59:51","guid":{"rendered":"http:\/\/nhub.news\/?p=3448976"},"modified":"2026-01-26T18:13:44","modified_gmt":"2026-01-26T16:13:44","slug":"microsoft-reports-an-issue-in-which-devices-are-failing-to-boot-after-downloading-the-latest-update","status":"publish","type":"post","link":"http:\/\/nhub.news\/fr\/2026\/01\/microsoft-reports-an-issue-in-which-devices-are-failing-to-boot-after-downloading-the-latest-update\/","title":{"rendered":"Microsoft reports &#039;an issue in which devices are failing to boot&#039; after downloading the latest update"},"content":{"rendered":"<p style=\"text-align: justify;\"><b>Another week, another big Windows problem.<\/b><br \/>\nIf you have downloaded January&rsquo;s KB5074109 Windows update and can&rsquo;t seem to get past boot, you aren&rsquo;t alone.<br \/>As reported by Windows Latest, Microsoft has updated users in a support document that it is \u00ab\u00a0investigating customer reports of device boot failures following the January 2026 update and later updates.\u00a0\u00bb<br \/>The document is only accessible by Microsoft 365 business accounts, which does seem to imply that it&rsquo;s business devices that are typically affected by this boot problem. However, so far, there&rsquo;s been no confirmation either way on which devices are affected.<br \/>The document says, \u00ab\u00a0Microsoft has received a limited number of reports of an issue in which devices are failing to boot with stop code &lsquo;UNMOUNTABLE_BOOT_VOLUME&rsquo;, after installing the January 2026 Windows security update (KB5074109), released January 13, 2026, and later updates. Affected devices show a black screen with the message &lsquo;Your device ran into a problem and needs a restart. You can restart.&rsquo; At this stage, the device cannot complete startup and requires manual recovery steps.\u00a0\u00bb<br \/>Typically, this error code tends to signify a problem with a boot drive (but can also happen due to corrupted files or even an issue with memory). However, this isn&rsquo;t the first time users have reported a Windows update being responsible for this error code.<br \/>This is not the only problem that has popped up in this month&rsquo;s updates. January 24 saw the launch of a surprise update, which patched an issue with apps becoming unresponsive when saving files on the cloud.<br \/>Microsoft has only indicated a &lsquo;limited&rsquo; number of reports, so we don&rsquo;t yet know how widespread this problem is. Microsoft does clarify that it is only currently happening to physical devices and hasn&rsquo;t been spotted on virtual machines. The issue is being investigated and seems to only impact those with the 26200.7623 and 26100.7623 Windows builds, or later.<br \/>You can check if your PC could be affected by going to &lsquo;Settings&rsquo;, then &lsquo;About&rsquo; and scrolling down to &lsquo;Windows info&rsquo;. The &lsquo;OS build&rsquo; section should tell you which build you&rsquo;re on. Naturally, if you aren&rsquo;t yet on the KB5074109 Windows update, I&rsquo;d advise holding off until Microsoft can diagnose the problem.<br \/>If, however, you have the update and have found yourself affected, you will have to use the Windows Recovery option or, worst-case scenario, go through a clean reinstall. The only thing worse than using Windows is installing Windows, but for casual users, there aren&rsquo;t many OSes to choose from. I&rsquo;ve been hearing Linux calling my name like the Green Goblin helmet for some time, and maybe 2026 is the year to finally put on the mask.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Another week, another big Windows problem. If you have downloaded January&rsquo;s KB5074109 Windows update and can&rsquo;t seem to get past boot, you aren&rsquo;t alone.As reported by Windows Latest, Microsoft has updated users in a support document that it is \u00ab\u00a0investigating customer reports of device boot failures following the January 2026 update and later updates.\u00a0\u00bbThe document [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3448975,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[93],"tags":[],"_links":{"self":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/3448976"}],"collection":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/comments?post=3448976"}],"version-history":[{"count":0,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/3448976\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media\/3448975"}],"wp:attachment":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media?parent=3448976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/categories?post=3448976"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/tags?post=3448976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}