About the latest Microsoft mess about the HDDs/SSDs getting corrupted, does the new Preview update KB5064081 fix the problem?
Probably not. For a severity-0 data loss issue, MS would issue an Out of Band (emergency) release. Your only current option is to pause WU, and roll back to a previous LCU.
Again, the SSD faillures did not have anything to do with the updates: https://forums.mydigitallife.net/posts/1888013 + https://forums.mydigitallife.net/posts/1888257 And yes, there is a new "evidence" video online, 16min of acting very scientific and then still it should be a phison problem as far as i was able to listen to that video.
Back to KB5063878, I hear that it's hard drives that have Phison NAND controllers that are affected. To the best of my knowledge (and I know, it is limited, but...) traditional hard disk drives don't use Phison NAND controllers and I use traditional hard disks, both internal and external. Is this wrong?
The problem isn't limited to Phison. Other SSDs have been recorded to have issues (like Samsung), and even some mechanical hard drives. To make matters worse, controllers used for SSDs might vary, even within the same brand/model.
I can't rollback because I just rewiped my hard drive with a Windows 11 that has the latest update slipstreamed. Do I just wait until Patch Tuesday while not do any heavy file transfers? So far, uninstalling KB5063878 is not an option.
Both Phison as Microsoft decline that there is a problem, both have been unable to reproduce the issue claimed
You wiped the drive for re-installing and now you can't rollback, wipe again? And do you even have the ssd problems at the moment or another related issue?
None so far, but I don't want to risk it, so I shall abstain from doing any large file transfers at the moment. No, i don't use SSDs.
@Enthousiast: The forum software is a bit b*tchy in this regard. When posts are moved over to a new topic, the oldest post (as of post date) automatically becomes OP. That means, as you opened the new topic at a later time, older posts moved into it shoved you down. This needs to be manually corrected, and, as far as I can see, already has been resolved. It's not disrespect, just technical restrictions. Remember, all moderation is live, and you probably checked in when it was not done, yet.
Of course it is a technical prohlem, only changed when i noticed it... don't bother to reply to this, getting a bit fed up with this new moderation atm.