{"id":38078,"date":"2025-05-17T00:01:25","date_gmt":"2025-05-16T22:01:25","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=38078"},"modified":"2025-05-15T23:32:42","modified_gmt":"2025-05-15T21:32:42","slug":"microsofts-unloved-refs-files-system-cpu-ram-utilization-bug-in-windows-server-2025-unfixed","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2025\/05\/17\/microsofts-unloved-refs-files-system-cpu-ram-utilization-bug-in-windows-server-2025-unfixed\/","title":{"rendered":"Microsoft's unloved ReFS files system – CPU\/RAM utilization bug in Windows Server 2025 unfixed"},"content":{"rendered":"

\"Windows\"[German<\/a>]The ReFS file system introduced by Microsoft in Windows a long time ago seems to be a \"stepchild\" of the developers. Bugs are never fixed – even with Windows Server 2025, the May 2025 patchday has not changed the problem that ReFS-formed disks lead to high CPU\/RAM utilization, making the server unusable.<\/p>\n

<\/p>\n

The Resilient File System (ReFS)<\/h2>\n

\"\"ReFS<\/a> was introduced by Microsoft as a \"new\" file system with the Windows 8 and Windows Server 2012 operating systems (see my German blog post Windows 8 Storage Space und ReFS<\/a>). In addition to compatibility with the NTFS file system, Microsoft promised many advantages such as a transaction model for maintaining consistency, including checking data when reading and writing, error tolerance through redundancy, auto-correction when data errors are detected, etc. Microsoft has published the article Resilient File System (ReFS) overview<\/a> with some explanations.<\/p>\n

Somehow an unbeloved stepchild<\/h2>\n

In view of the advantages outlined above and its introduction over a decade ago, ReFS should actually be the \"philosopher's stone\" for Microsoft. To me, however, ReFS seems more like a stepchild that is hidden away and not particularly cared for.<\/p>\n

With the Fall Creators Update (version 1709), the creation of new partitions with ReFS was partially canceled for Windows 10 (see Windows 10 Version 1709: ReFS will be removed (partially)<\/a>). Such data carriers can now only be created in the Enterprise and Pro for Workstations versions.<\/p>\n

In addition, administrators who format disks with the ReFS file system repeatedly run into bugs that are not fixed for a long time. I remind you of my blog posts Out-of-Band Updates for Windows (Jan. 17\/18, 2022) doesn't fixes ReFS Issues complete<\/a> andMicrosoft and the unfixed ReFS bug in Windows<\/a>. Microsoft is just an \"innovative company\" that wants to be ahead in AI, so such lowlights are of no interest.<\/p>\n

Windows Server 2025 and the ReFS bug<\/h2>\n

There is a nasty bug in the ReFS file system in Windows Server 2025, Microsoft's flagship server product. Blog reader Daniel A. noted in this German comment<\/a>t: \"Too bad, the ReFS problem under Server 2025 is apparently not being addressed\". The bug was not fixed with the May 2025 updates either.<\/p>\n

Regarding the ReFS bug, Daniel wrote in another German comment<\/a> that under Windows Server 2025, in conjunction with ReFS-formatted drives, there is a massive utilization of CPU\/RAM. This probably goes so far that the server becomes unusable after a short time, it depends on how much CPU\/RAM is installed.<\/p>\n

According to readers, the bug was confirmed by Microsoft to the backup provider Veeam. In the Veeam forum there is a discussion in the thread Server 2025 – high CPU and RAM<\/a> – and in this thread<\/a> someone blames it on a cache limit.<\/p>\n

The reader states that Microsoft has probably sent the Veeam developers a patch that is not publicly available (presumably for testing). According to Daniel A., however, this fix – at least according to the KB articles – was not rolled out in the cumulative update for Windows Server 2025 on May 13, 2025. If I look at the blog posts linked below, the bug could be dormant in Windows Server 2025 for even longer. Or does anyone have other information?<\/p>\n

Similar articles:<\/strong>
\nWindows 8: Neuigkeiten zum ReFS-Dateisystem<\/a>
\nWindows 10 Version 1709: ReFS will be removed (partially)<\/a>
\nOut-of-Band Updates for Windows (Jan. 17\/18, 2022) doesn't fixes ReFS Issues complete<\/a>
\nMicrosoft and the unfixed ReFS bug in Windows<\/a>
\nWindows 11 24H2\/Server 2025 with huge Hyper-V bug?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]The ReFS file system introduced by Microsoft in Windows a long time ago seems to be a \"stepchild\" of the developers. Bugs are never fixed – even with Windows Server 2025, the May 2025 patchday has not changed the problem … Continue reading →<\/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,2],"tags":[47,980,2845],"class_list":["post-38078","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-issue","tag-refs","tag-windows-server-2025"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38078","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=38078"}],"version-history":[{"count":5,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38078\/revisions"}],"predecessor-version":[{"id":38083,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/38078\/revisions\/38083"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=38078"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=38078"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=38078"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}