The news Windows File Recovery tool is available in the Microsoft Store. It can recover deleted files and attempt to make sense of corrupted ones. It does a good enough job to be worth downloading, installing and learning.
In a welcome effort to reduce the number of Windows 10 reset, refresh and reinstall options, MS does away with “Fresh Start” in Version 2004, and directs users to “Reset this PC” instead. Good move!
When I stop tearing what little hair out I still have left, I remember that the Microsoft Support and Recovery Assistant (SaRA) can fix Outlook problems. In this case, it can and it does, and I regain access to my Exchange server in Outlook. Problem solved!
Before I start messing around with my production PC I always make sure I have a current backup. So why am I not surprised that my current backup is now on a drive that itself needs recovery? Sigh.
On systems with Secure Boot enabled and BitLocker encrypted system boot drives, it’s necessary to turn off Secure Boot to start up from alternate media (like a USB Flash drive). When that’s over and done with, you have to turn Secure Boot back on to avoid being forced to enter the 40-charactrer BitLocker key. Sigh.
By taking some quick protective measures against boot issues, blue screens, or unwanted file deletion, you can easily avoid certain problems that have been widely reported for some recent Cumulative Updates (CUs) for Windows 10.
Normally, when I write about free or commercial software for Win10.Guru, it falls under the heading of Admin Toolkit items. This time, I came across something free and worthy of mention that I wanted to share. But I haven’t had enough time or experience with the tool to know if I can recommend it or
Happily it turns out that Settings MIA in Windows 10 Release Preview has an easy fix: restart Windows Explorer.
Working with WinRE in Windows 10, I learn that recovery media is a snapshotting mechanism that will restore your system to its state when the snapshot was made. I can do better than that, with Macrium Reflect.
In looking at the differences between the new Feature Upgrade C:\Windows folder for Build 19546 verus its Windows.old “equivalent” (Build 19541), I couldn’t help but notice more that was different than alike. Start with the intro image for this story. Windows.old (left) includes 86,332 files and 22,148 folders and is 15.3 GB in size (15.1