{"id":38931,"date":"2025-08-16T00:01:34","date_gmt":"2025-08-15T22:01:34","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=38931"},"modified":"2025-08-17T12:09:25","modified_gmt":"2025-08-17T10:09:25","slug":"windows-server-2025-hpe-proliant-dl325-server-drops-irql_not_less_or_equal-bsod-after-july-2025-update","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/08\/16\/windows-server-2025-hpe-proliant-dl325-server-drops-irql_not_less_or_equal-bsod-after-july-2025-update\/","title":{"rendered":"Windows Server 2025: HPE ProLiant DL325 server drops IRQL_NOT_LESS_OR_EQUAL BSOD after July 2025 update"},"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\/08\/15\/windows-server-2025-hpe-proliant-dl325-server-error-irql-not-less-or-equal\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]I'm going to include a post here in the blog that a blog reader described to me a few days ago. An HPE ProLiant DL325 Gen10 Plus v2 running Windows Server 2025 triggers IRQL_NOT_LESS_OR_EQUAL blue screens (stop code 0x0000000a) in ntoskrnl.exe as soon as the July 2025 updates (KB5062553 ff.) are installed. This does not appear to be an isolated case, as I have received two further reports from readers via the Internet. The cause could be incompatibilities with AMD processors, but nothing is known yet.<\/p>\n<p><!--more--><\/p>\n<h2>Reader tip about BSOD in Windows Server 2025<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/517cabd1ca854b7bb59a208c4b5999ff\" alt=\"\" width=\"1\" height=\"1\" \/>Blog reader Marco M. from Swiss had already contacted me in July 2025, but due to vacations and other circumstances, the issue was put on hold. He had serious issues with BSOD on Windows Server 2025, caused by July 2025 updates.<\/p>\n<h3>Initial situation with Windows Server 2025 on HPE servers<\/h3>\n<p>The initial situation involves the following HPE server models, which are operated in the reader's data center:<\/p>\n<ul>\n<li>ProLiant DL325 Gen10 Plus v2 with \"AMD EPYC 7443P 24-core processor\"<\/li>\n<li>ProLiant DL325 Gen10 with \"AMD EPYC 7402P 24-core processor\"<\/li>\n<\/ul>\n<p>Windows Server 2025 is installed directly on the hardware on the HPE servers, so these are not virtual servers.<\/p>\n<h3>Everything fine until the June 2025 updates<\/h3>\n<p>In the initial report, the reader stated that all machines running Windows Server 2025 that had been patched up to update <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/june-10-2025-kb5060842-os-build-26100-4349-d7d4793c-bb41-4e4a-bfbd-a0dbdb2f6055\" target=\"_blank\" rel=\"noopener\">KB5060842<\/a> (OS Build 26100.4349) from June 10, 2025, were running smoothly and had no problems.<\/p>\n<h3>July 2025 updates trigger BlueScreen<\/h3>\n<p>After installing cumulative update <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/july-8-2025-kb5062553-os-build-26100-4652-0e8c636a-7712-4936-9c76-ece21a38cf9a\" target=\"_blank\" rel=\"noopener\">KB5062553<\/a> (OS Build 26100.4652) from July 8, 2025, the server starts normally until the login screen. But then, after a few minutes, a BSOD appears with the following error message (stop code 0x0000000a):<\/p>\n<blockquote><p>Stop Code: IRQL_NOT_LESS_OR_EQUAL<br \/>\nWhat failed: ntoskrnl.exe<\/p><\/blockquote>\n<p>Installing the out-of-band update <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/july-13-2025-kb5064489-os-build-26100-4656-out-of-band-6d701323-0247-482a-98ae-6b23032fa45f\" target=\"_blank\" rel=\"noopener\">KB5064489<\/a> (OS Build 26100.4656) from July 13, 2025 did not change this situation \u2013 the BlueScreen continues to appear.<\/p>\n<h3>Reinstallation, update, and BSOD again<\/h3>\n<p>The blog reader then reinstalled Windows Server 2025 on a machine without configuring any parameters. The installation was successful, and the machine ran without errors. The reader then started Windows Update and reinstalled the cumulative update <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/july-8-2025-kb5062553-os-build-26100-4652-0e8c636a-7712-4936-9c76-ece21a38cf9a\" target=\"_blank\" rel=\"noopener\">KB5062553<\/a> (OS Build 26100.4652) from July 8, 2025. The process ran smoothly and without errors, so the server was restarted. Shortly after the user logged in, a BlueScreen appeared again:<\/p>\n<blockquote><p>Stop Code: IRQL_NOT_LESS_OR_EQUAL<br \/>\nWhat failed: ntoskrnl.exe<\/p><\/blockquote>\n<p>After the July 2025 update <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/july-8-2025-kb5062553-os-build-26100-4652-0e8c636a-7712-4936-9c76-ece21a38cf9a\" target=\"_blank\" rel=\"noopener\">KB5062553<\/a> at the latest, Windows Server 2025 crashes with BSOD on the above-mentioned HPE servers. This does not appear to be an isolated case.<\/p>\n<h2>First report on reddit.com<\/h2>\n<p>The blog reader wrote to me in his initial email that he had only found one article on reddit.com titled <a href=\"https:\/\/www.reddit.com\/r\/sysadmin\/comments\/1lyn67z\/potential_issues_with_windows_server_2025_june\/\" target=\"_blank\" rel=\"noopener\">Potential Issues with Windows Server 2025 June 2025 Update<\/a> that described the same problem. In the case described, Windows Server 2025 was installed on a Supermicro H12SSL-i, AMD EPYC 7313. This installation of Windows Server 2025 worked flawlessly until build 26100.1742.240906-0331.<\/p>\n<p>After the user upgraded to the cumulative update from June 2025, Windows Server 2025 could no longer boot because a BSOD occurred in ntoskrnl.exe. Here, the affected party\u00a0 also attempted to reinstall Windows Server 2025, but again received a BSOD. At first, the affected party thought it might have something to do with an additional RAID card, Mellanox Connectx-5, or 2 x U.2 NVMe's. These were removed and reinstalled. Windows Server 2025 was installed on a Samsung PM983 M.2 NVMe.<\/p>\n<p>The person affected writes that he has seen Proxmox users report a similar problem with Server 2025 VMs (see also <a href=\"https:\/\/borncity.com\/win\/2025\/06\/18\/windows-11-server-2025-june-2025-updates-cause-bsod-in-proxmox-kvm-qemu\/\" rel=\"bookmark\">Windows 11\/Server 2025 June 2025 updates cause BSOD in Proxmox\/KVM\/QEMU<\/a>), but nothing about bare metal installations. So far, there has been no indication of the cause in this thread, at least from what I have seen from skimming through it.<\/p>\n<h2>Report at Microsoft Q&amp;A<\/h2>\n<p>On August 14, 2025, the blog reader contacted me again by email and pointed me to the next hit with the title <a href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5513064\/after-i-install-update-kb5062553-geting-bsod-irql\" target=\"_blank\" rel=\"noopener\">After I install update KB5062553 geting BSOD &#8211; IRQL NOT LESS OR EQUAL, Windows 2025<\/a>\u00a0 from August 4, 2025 on Microsoft Q&amp;A.<\/p>\n<p>There is also a problem with Windows Server 2025, which triggers a BSOD with the stop code: IRQL NOT LESS OR EQUAL in <em>ntoskrnl.exe<\/em> after installing the latest update (KB5062553 from July 8, 2025). According to the person affected, this problem occurs on several computers after the update.<\/p>\n<p>Here, too, it is said that reinstalling Windows Server 2025 helps and the system runs until the June 2025 update KB5062553 is installed. Then the BSOD reappears after a restart. Reinstalling the drivers and updating the BIOS did not help.<\/p>\n<blockquote><p>The Q&amp;A post contains a link to a mini dump, which I viewed using Nirsoft BlueScreen Viewer. However, this does not provide any further information. A complete dump will probably need to be extracted and analyzed in Windows Debugger in order to narrow down the cause.<\/p><\/blockquote>\n<h2>Report in the Thomas Krenn Wiki<\/h2>\n<p>After I finally posted this article online, a reader pointed me to a wiki article by Thomas Krenn on BlueSky (thanks for the tip).<\/p>\n<p><a href=\"https:\/\/www.thomas-krenn.com\/en\/wiki\/Windows_Update_KB5062553_causes_IRQL_NOT_LESS_OR_EQUAL\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" class=\"\" src=\"https:\/\/i.postimg.cc\/8CDPVHJb\/image.png\" alt=\"Windows Server 2025 BSOD after July 2025 update\" width=\"523\" height=\"241\" \/><\/a><\/p>\n<p>An undated post titled <a href=\"https:\/\/www.thomas-krenn.com\/en\/wiki\/Windows_Update_KB5062553_causes_IRQL_NOT_LESS_OR_EQUAL\" target=\"_blank\" rel=\"noopener\">Windows Update KB5062553 causes IRQL NOT LESS OR EQUAL<\/a> it is confirmed, that on Supermicro H12 motherboards:<\/p>\n<ul>\n<li>Supermicro H12SSL-NT<\/li>\n<li>Supermicro H12SSL-CT<\/li>\n<li>Supermicro H12SSL-i<\/li>\n<\/ul>\n<p>since installing the July 2025 updates (KB5062553, ff.), the above BSOD occurs. An unofficial workaround is to uninstall the relevant updates \u2013 but this isn't ideal, as it doesn't fix the vulnerabilities. I'll try to report the problem to Microsoft.<\/p>\n<h2>Root cause analysis: TPM and UEFI ruled out<\/h2>\n<p><strong>Addendum: <\/strong>Within my German blog, some wild theories were discussed in some comments, suggesting that TPM was the root cause or that it could be related to UEFI issues. Here a few more insights.<\/p>\n<h3>Another test and new findings<\/h3>\n<p>Swiss blog reader Marco M. subsequently sent me information that he had run a new test with a \"ProLiant DL325 Gen10\" system with an \"AMD EPYC 7402P 24-core processor\" in legacy BIOS mode. Windows Server 2025 was installed in the standard desktop version from a USB stick using the following ISO file:<\/p>\n<pre>SW_DVD9_Win_Server_STD_CORE_2025_24H2.8_64Bit_German_DC_STD_MLF_X24-07260.ISO<\/pre>\n<p>The installation went smoothly, the user logged in once and left the installation \"untouched.\" Then a restart was performed and the system waited until the latest Windows Update KB5063878 for Windows Server 2025 (OS Build 26100.4946) from August 12, 2025 was installed. The system was restarted, and the progress bar was at 30%, so everything seemed fine. The second phase of the update began, with the progress bar moving from 30% to 100%. Everything looked good until, after a few minutes, the following familiar message appeared.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" title=\"Windows Server 2025 IRQL_NOT_LESS_OR_EQUAL-BSOD \" src=\"https:\/\/i.postimg.cc\/L4yZKhh5\/image.png\" alt=\"Windows Server 2025 IRQL_NOT_LESS_OR_EQUAL-BSOD \" width=\"428\" height=\"306\" \/><\/p>\n<p>The reader wrote, \"This means that a BOSD is also issued in Legacy BIOS mode, which should rule out a problem with UEFI, with or without Secure Boot and TPM.\" In the screenshot above, Wof.sys is listed as the component causing the problem. The abbreviation stands for Windows Overlay Filter, and the sys file is a filter driver used for compressed image files in Windows (see <a href=\"https:\/\/support.microsoft.com\/en-us\/topic\/you-cannot-compress-windows-image-files-because-of-memory-leak-in-windows-8-1-721851b7-14a3-1eb6-c3b4-b96a42ad60cb\" target=\"_blank\" rel=\"noopener\">this Microsoft Support article<\/a>).<\/p>\n<p>There are numerous posts on the Internet that deal with fixing BlueScreens related to the driver. However, in the current case, this leads nowhere, as the reader wrote: \"Possibly a driver problem with Wof.sys? Wof.sys is output.\" This refers to the BlueScreen display where the driver is named. But the reader showed me the properties of the driver:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/i.postimg.cc\/CKL9BvHw\/image.png\" alt=\"Wof.sys Eigenschaften Windows Server 2025\" width=\"640\" height=\"403\" \/><\/p>\n<p>The driver is very up to date, dated July 16, 2025, and digitally signed by Microsoft. There's no point in messing around with it.<\/p>\n<h3>Attempt analysis with WinDbg and BlueScreen Viewer<\/h3>\n<p>I found a minidump in Microsoft Q&amp;A in the post titled <a href=\"https:\/\/learn.microsoft.com\/en-us\/answers\/questions\/5513064\/after-i-install-update-kb5062553-geting-bsod-irql\" target=\"_blank\" rel=\"noopener\">After I install update KB5062553 geting BSOD &#8211; IRQL NOT LESS OR EQUAL, Windows 2025<\/a> from August 4, 2025. In my old German article series <a href=\"https:\/\/www.borncity.com\/blog\/2012\/02\/03\/windows-bluescreen-analyse-teil-3\/\" target=\"_blank\" rel=\"noopener ugc\">Windows BlueScreen-Analyse \u2013 Teil 3<\/a> from 2012, I outlined the possibilities for analyzing dump files that generate BlueScreens.<\/p>\n<p>Therefore, the mini dump mentioned above was downloaded and imported into NirSoft BlueScreen Viewer. However, it did not reveal anything beyond the above findings that <em>ntoskrnl.exe<\/em> was involved.<\/p>\n<p>I then installed the Windows debugger WinDBG from the Store on a Windows 10 notebook and analyzed the mini dump there. I had stated in the German <a href=\"https:\/\/www.borncity.com\/blog\/2025\/08\/15\/windows-server-2025-hpe-proliant-dl325-server-error-irql-not-less-or-equal\/#comment-227029\" target=\"_blank\" rel=\"noopener\">comment here<\/a> that memory access to an invalid address triggers the BSOD. The output from the Windows Debugger led me to a discussion in the <a href=\"https:\/\/learn.microsoft.com\/en-ie\/answers\/questions\/2282592\/bsod-irql-not-less-or-equal\" target=\"_blank\" rel=\"noopener\">BSOD IRQL_NOT_LESS_OR_EQUAL<\/a> thread from June 2025 during a web search.<\/p>\n<p>But it didn't help, because I didn't know the boundary conditions, <em>MsMpEng.exe<\/em> was named as the cause, and I couldn't access the dump files hosted on online stores. So the suggestion from the German <a href=\"https:\/\/www.borncity.com\/blog\/2025\/08\/15\/windows-server-2025-hpe-proliant-dl325-server-error-irql-not-less-or-equal\/#comment-227088\" target=\"_blank\" rel=\"noopener\">comment here<\/a> wasn't feasible \u2013 whether it would have helped is anyone's guess.<\/p>\n<p>On the one hand, I welcome the many discussions and assumptions expressed by my German blog readers. I want to make use of the collective intelligence of the readership and had hoped for the \"I have that too, it's because of&#8230;\" effect. Unfortunately, one problem is the \"comment noise\" caused by assumptions, which quickly dilute everything so that the core message is lost. An no, I don't got a clue, what's the root cause.<\/p>\n<p>To summarize these discussions and assumptions, here is some concluding information. I would also evaluate a complete dump in the debugger, but I'm not sure if that would lead anywhere. However, the blog reader provided me with some additional information. In his test outlined above, with a new installation of Windows Server 2025 in Legacy BIOS mode before installing the August 2025 security update, he set the option \"Complete memory dump\" under \"Save information\" in the system settings (Control Panel,<em> System and Security, System, Advanced System Settings, Advanced<\/em> tab, \"Startup and Recovery\" category) under \"Save information,\" he had set the option \"Complete memory dump.\"<\/p>\n<p>This should generate a complete memory dump when a Blue Screen occurs. The reader's information was as follows: \"Although 'Complete Memory Image' was set for debugging before the KB, Windows Server 2025 does not create this memory dump file when a BSOD occurs. He only received a DumpStack.log file with the following content.<\/p>\n<pre>DLOGFILE00010000DUMP=\u0012 \r\nDump stack initialized at UTC: 2025\/08\/16 15:19:49, local time: 2025\/08\/16 17:19:49.\r\n#BugCheckCode 0x00000000000000D1\r\n#BugCheckP1 0xFFFFBB84D4140000\r\n#BugCheckP2 0x00000000000000FF\r\n#BugCheckP3 0x0000000000000000\r\n#BugCheckP4 0xFFFFF80765ED05E6\r\nProgress 0x00000042\r\nElapsed BugCheck duration 00185191ms\r\nStarting get secondary dump callbacks size.\r\nProgress 0x00000052\r\nFinish get secondary dump callbacks size.\r\nDump Type: 5, Total Dump Size: 68556454254, Secondary Dump Size: 84334.\r\nStarting write of dump header.\r\nFinish write of dump header.\r\nStarting write of full bitmap dump header.\r\nFinish write of bitmap dump header.\r\nStarting write of memory dump data.\r\nElapsed BugCheck duration 00185232ms\r\nDumping physical memory to disk: 0% \r\nDumping physical memory to disk: 5% \r\nDumping physical memory to disk: 10% \r\nDumping physical memory to disk: 15% \r\nDumping physical memory to disk: 20% \r\nDumping physical memory to disk: 25% \r\nDumping physical memory to disk: 30% \r\nDumping physical memory to disk: 35% \r\nDumping physical memory to disk: 40% \r\nDumping physical memory to disk: 45% \r\nDumping physical memory to disk: 50% \r\nDumping physical memory to disk: 55% \r\nDumping physical memory to disk: 60% \r\nDumping physical memory to disk: 65% \r\nDumping physical memory to disk: 70% \r\nDumping physical memory to disk: 75% \r\nDumping physical memory to disk: 80% \r\nDumping physical memory to disk: 85% \r\nDumping physical memory to disk: 90% \r\nDumping physical memory to disk: 95% \r\nDumping physical memory to disk: 100% \r\nFinish write of bitmap dump data. Total pages:16736865 Pages written:16736865\r\nProgress 0x00000043\r\nElapsed BugCheck duration 00286745ms\r\nStarting invoking secondary dump callbacks.\r\nCalling CRASHDUMP secondary callback.\r\nReturn from CRASHDUMP secondary callback.\r\nWriting CRASHDUMP secondary callback data.\r\nWriting CRASHDUMP secondary callback data done.\r\nCalling USBXHCI secondary callback.\r\nReturn from USBXHCI secondary callback.\r\nWriting USBXHCI secondary callback data.\r\nWriting USBXHCI secondary callback data done.\r\nCalling IoBugCheckDriverData secondary callback.\r\nReturn from IoBugCheckDriverData secondary callback.\r\nWriting IoBugCheckDriverData secondary callback data.\r\nWriting IoBugCheckDriverData secondary callback data done.\r\nCalling PortDriverStandard secondary callback.\r\nReturn from PortDriverStandard secondary callback.\r\nWriting PortDriverStandard secondary callback data.\r\nWriting PortDriverStandard secondary callback data done.\r\nCalling \\Device\\DxgKrnl secondary callback.\r\nReturn from \\Device\\DxgKrnl secondary callback.\r\nWriting \\Device\\DxgKrnl secondary callback data.\r\nWriting \\Device\\DxgKrnl secondary callback data done.\r\nCalling Wdf01000 secondary callback.\r\nReturn from Wdf01000 secondary callback.\r\nWriting Wdf01000 secondary callback data.\r\nWriting Wdf01000 secondary callback data done.\r\nCalling blackbox - CI secondary callback.\r\nReturn from blackbox - CI secondary callback.\r\nWriting blackbox - CI secondary callback data.\r\nWriting blackbox - CI secondary callback data done.\r\nCalling blackbox - NTFS secondary callback.\r\nReturn from blackbox - NTFS secondary callback.\r\nWriting blackbox - NTFS secondary callback data.\r\nWriting blackbox - NTFS secondary callback data done.\r\nCalling blackbox - BSD secondary callback.\r\nReturn from blackbox - BSD secondary callback.\r\nWriting blackbox - BSD secondary callback data.\r\nWriting blackbox - BSD secondary callback data done.\r\nCalling secondary multi-part dump callbacks.\r\nStarting TRIAGEDUMPDATA multi-part secondary callback.\r\nFinish TRIAGEDUMPDATA multi-part secondary callback.\r\nStarting SMBiosData multi-part secondary callback.\r\nFinish SMBiosData multi-part secondary callback.\r\nStarting SMBiosRegistry multi-part secondary callback.\r\nFinish SMBiosRegistry multi-part secondary callback.\r\nStarting SMBiosRegisters multi-part secondary callback.\r\nFinish SMBiosRegisters multi-part secondary callback.\r\nStarting SMBiosDataACPI multi-part secondary callback.\r\nFinish SMBiosDataACPI multi-part secondary callback.\r\nStarting PCI multi-part secondary callback.\r\nFinish PCI multi-part secondary callback.\r\nStarting Etw multi-part secondary callback.\r\nFinish Etw multi-part secondary callback.\r\nFinish calling secondary multi-part dump callbacks.\r\nProgress 0x00000045\r\nFinish invoking secondary dump callbacks.\r\nStarting invoking dump complete callbacks; Type: 0x04.\r\nFinished invoking dump complete callbacks; Type: 0x04.\r\nProgress 0x00000046\r\nDump ended at UTC: 2025\/08\/16 15:19:49, local time: 2025\/08\/16 17:19:49.\r\nElapsed BugCheck duration 00286753ms\r\nProgress 0x00000053\r\nDump completed successfully.<\/pre>\n<p>But I didn't get anywhere with that either. I'll try to pass the whole thing on to Microsoft. Something is seriously broken there, so the developers should take care of it.<\/p>\n<p><strong>Similar article:<\/strong><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2025\/06\/11\/patchday-windows-server-updates-june-10-2025\/\">Patchday: Windows Server-Updates (June 10, 2025)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2025\/06\/18\/windows-11-server-2025-june-2025-updates-cause-bsod-in-proxmox-kvm-qemu\/\" rel=\"bookmark\">Windows 11\/Server 2025 June 2025 updates cause BSOD in Proxmox\/KVM\/QEMU<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2025\/06\/13\/windows-11-24h2-out-of-band-update-kb5063060\/\" rel=\"bookmark\">Windows 11 24H2: Out-of-Band Update KB5063060<\/a><br \/>\n<a href=\"https:\/\/www.borncity.com\/blog\/2025\/06\/27\/windows-11-22h2-24h2-preview-updates-verfuegbar\/\" rel=\"bookmark\">Windows 11 22H2 \u2013 24H2 Preview-Updates verf\u00fcgbar<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2025\/07\/19\/windows-10-11-and-server-known-issues-early-july-2025\/\">Windows 10\/11 and Server: Known issues (early July 2025)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]I'm going to include a post here in the blog that a blog reader described to me a few days ago. An HPE ProLiant DL325 Gen10 Plus v2 running Windows Server 2025 triggers IRQL_NOT_LESS_OR_EQUAL blue screens (stop code 0x0000000a) in &hellip; <a href=\"https:\/\/borncity.com\/win\/2025\/08\/16\/windows-server-2025-hpe-proliant-dl325-server-drops-irql_not_less_or_equal-bsod-after-july-2025-update\/\">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":[463,580,22,2],"tags":[47,69,195,2845],"class_list":["post-38931","post","type-post","status-publish","format-standard","hentry","category-issue","category-security","category-update","category-windows","tag-issue","tag-security","tag-update","tag-windows-server-2025"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38931","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=38931"}],"version-history":[{"count":6,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38931\/revisions"}],"predecessor-version":[{"id":38950,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38931\/revisions\/38950"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=38931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=38931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=38931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}