{"id":37158,"date":"2025-02-17T08:22:07","date_gmt":"2025-02-17T07:22:07","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=37158"},"modified":"2025-02-17T08:28:11","modified_gmt":"2025-02-17T07:28:11","slug":"windows-server-2025-iscsi-boot-device-inaccessible-fixed","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/02\/17\/windows-server-2025-iscsi-boot-device-inaccessible-fixed\/","title":{"rendered":"Windows Server 2025: iSCSI \"Boot Device inaccessible\" fixed"},"content":{"rendered":"<p><img decoding=\"async\" style=\"margin: 0px 10px 0px 0px; display: inline; float: left;\" title=\"Windows\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2021\/04\/Windows-klein.jpg\" alt=\"Windows\" width=\"200\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2025\/02\/17\/windows-server-2025-iscsi-boot-device-inaccessible-gefixt\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Since the release of Windows Server 2025, a boot problem in iSCSI environments was confirmed by Microsoft as a known issue. Microsoft has now provided a fix for this problem on February 11, 2025 and lists the issue as resolved. This can be seen from an entry on the relevant Microsoft Windows Release Health dashboard.<\/p>\n<p><!--more--><\/p>\n<h2>iSCSI \"Boot Device inaccessible\" Bug<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg02.met.vgwort.de\/na\/bd80fbc030414fdd926a7b9941191e0e\" alt=\"\" width=\"1\" height=\"1\" \/>In the blog post <a href=\"https:\/\/borncity.com\/win\/2024\/11\/17\/windows-server-2025-unfinished-and-buggy\/\">Windows Server 2025: Unfinished and buggy?<\/a> on November 7, 2024, I pointed out that the Microsoft product \"Windows Server 2025\" released at that time had numerous problems. At the time, a blog reader gave me his first impressions of Windows Server 2025, which was released on November 1, 2024. There is also a reference to known issues, which were confirmed by Microsoft. There I had linked the support article <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/release-health\/status-windows-server-2025#479msgdesc\" target=\"_blank\" rel=\"noopener\" data-linktype=\"self-bookmark\">Error 'boot device inaccessible' might appear in iSCSI environments<\/a> and wrote \"It's not exactly trivial when I get a boot device inaccessible error &#8230;\".<\/p>\n<p>The problem: Servers that use iSCSI (Internet Small Computer Systems Interface) technology may display an error with the message \"Boot device inaccessible\" at startup.<\/p>\n<p>This can occur with servers operating in NDIS poll mode and booting from an iSCSI LUN. In such a configuration, the error occurs when the server starts up after the installation of Windows Server 2025 is complete. I don't know how common this combination is yet.<\/p>\n<h2>Fix for iSCSI \"Boot Device inaccessible\" bug<\/h2>\n<p>Microsoft has now updated the support article <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/release-health\/status-windows-server-2025#479msgdesc\" target=\"_blank\" rel=\"noopener\" data-linktype=\"self-bookmark\">Error 'boot device inaccessible' might appear in iSCSI environments<\/a> in the Known Issues of the Windows Server 2025 Release Health Dashboard on February 11, 2025 and set the status to \"Resolved\".<\/p>\n<p>This problem was fixed by the Windows updates of February 11, 2025 (<a href=\"https:\/\/aka.ms\/WinServer2025\/5051987\" target=\"_blank\" rel=\"noopener\" data-linktype=\"external\">KB5051987<\/a>) and later (see also <a href=\"https:\/\/borncity.com\/win\/2025\/02\/12\/patchday-windows-server-updates-february-11-2025\/\" rel=\"bookmark\">Patchday: Windows Server-Updates (February 11, 2025)<\/a>). In the support article, I cannot find any reference to this fix. Microsoft recommends that Windows Server 2025 administrators install the latest update, as it contains important improvements and fixes, including this issue.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Since the release of Windows Server 2025, a boot problem in iSCSI environments was confirmed by Microsoft as a known issue. Microsoft has now provided a fix for this problem on February 11, 2025 and lists the issue as resolved. &hellip; <a href=\"https:\/\/borncity.com\/win\/2025\/02\/17\/windows-server-2025-iscsi-boot-device-inaccessible-fixed\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1319],"tags":[],"class_list":["post-37158","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/37158","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=37158"}],"version-history":[{"count":3,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/37158\/revisions"}],"predecessor-version":[{"id":37161,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/37158\/revisions\/37161"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=37158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=37158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=37158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}