-
- Chief Product Officer
- Posts: 32373
- Liked: 7726 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
[ReFS] BSOD after installing March 2025 Cumulative Update
Please be aware of the newly introduced ReFS regression that may cause your backup repositories to BSOD. We have updated (right at the top) the ReFS Known Issues, Considerations, and Limitations support KB article with the latest information we received from Microsoft. This seems to affect all supported Windows versions.
This is all we know about the issue at the moment.
Thanks
This is all we know about the issue at the moment.
Thanks
-
- Veteran
- Posts: 1267
- Liked: 456 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Thank you very much for this warning.
Does this also happen when ReFS filesystems are attached but there is nearly no IO to these? We just finished migrating to XFS but our old repos are still attached to our main Veeam server.
I wonder: Has something like this ever happened with XFS?
Does this also happen when ReFS filesystems are attached but there is nearly no IO to these? We just finished migrating to XFS but our old repos are still attached to our main Veeam server.
I wonder: Has something like this ever happened with XFS?
-
- Chief Product Officer
- Posts: 32373
- Liked: 7726 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Unfortunately the above is literally all we know about the issue at the moment, no further details have been provided by Microsoft.
-
- Veeam Software
- Posts: 2833
- Liked: 647 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Wanted to comment on this as from my time in Support, I can only recall 2 times when XFS was a factor in significant issues in the Veeam infrastructure; one time ended up being an issue in the distribution (Ubuntu, EDIT: issue was identified as this, already patched in Ubuntu) and the other ended up being an /etc/fstab misconfiguration unrelated to XFS that was hard to spot (Veeam logging helped catch it though)
XFS has proven to be exceptionally reliable and resilient, so while I wouldn't say XFS is immune to such issues, it seems quite battle-tested.
David Domask | Product Management: Principal Analyst
-
- Veteran
- Posts: 1267
- Liked: 456 times
- Joined: Dec 17, 2015 7:17 am
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Really impressive.
This all shows that Veeam has really put its bets on the right horse. The posibility of using LVM alone has made our live so much better.
Thank you!!!
This all shows that Veeam has really put its bets on the right horse. The posibility of using LVM alone has made our live so much better.
Thank you!!!
-
- Service Provider
- Posts: 3
- Liked: 1 time
- Joined: Dec 08, 2016 6:31 pm
- Full Name: Luke Day
- Location: New Zealand
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Does anyone know if this was actually resolved in one of the subsequent CUs?
Cheers
Cheers
-
- Influencer
- Posts: 18
- Liked: 2 times
- Joined: Mar 06, 2023 3:53 pm
- Full Name: Brandon Halloran
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
Want to Bump this. Has this been resolved with Windows newer cumulative updates?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Jun 07, 2025 6:26 am
- Full Name: lilycollins
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
While we wait for a patch or more information from Microsoft, does your team recommend any interim solutions to mitigate the risk of BSOD when using ReFS?Gostev wrote: ↑Apr 11, 2025 9:59 am Unfortunately the above is literally all we know about the issue at the moment, no further details have been provided by Microsoft Among Us Online
-
- Chief Product Officer
- Posts: 32373
- Liked: 7726 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [ReFS] BSOD after installing March 2025 Cumulative Update
According to the KB article linked in the first post, this issue was supposedly resolved with April Windows updates.
Who is online
Users browsing this forum: Baidu [Spider], Semrush [Bot] and 30 guests