The most common reason Windows prompts you to perform the scan and fix is because the removable media in question was not properly unmounted and removed from Windows the last time it was used. The warning itself is a bit cryptic, however, as it’s a catch all for multiple issues. RELATED: Do You Really Need to Safely Remove USB Flash Drives? Scan the drive now and fix it.” Back in Windows 7 and Windows Vista, it prompt you with “Do you want to scan and fix Removable Disk ?” In Windows 8 it will warn you, as you saw, “There’s a problem with this drive. What’s the deal? Is my SD card going to be ruined or my files missing if I don’t scan and fix the drive? What exactly does it do?Īlthough the warning has changed slightly in appearance, Windows has been issuing these warnings for a long time. The error message must be there for a reason, but my files always look fine. I copied the pictures, pull the SD card out, put it back in my camera, and then the next time I needed to copy files the exact same thing happened.
Scan the drive now and fix it.” I didn’t click on the pop up box and then a few seconds the SD card automatically opened in Windows Explorer and my pictures were there like I expected. When I take the SD card out of my camera and plug it into my computer, a little box pops up that says “There’s a problem with this drive. Does something actually need fixing? Are you risking anything by ignoring the nagging to scan and fix the drive? Read on as we explain what the message means, if you should heed it, and how to keep it from coming back. I boot Linux if I'm coding).It’s a common sight for many Windows users: you pop in your flash drive or the memory card from your camera and Windows insists there is some problem that needs fixing. The problem is I don't often switch back & forth on this machine so I don't know if maybe 14.04 is the culprit (it defaults to Windows as it's my gaming machine. Things were definitely fine with Ubuntu 13.10, but now I'm on 14.04. Now obviously the error is bogus (since a mere reboot fixes it without me reconnecting this magical invisible device that is so important to booting), but I'm wondering if maybe Ubuntu or Microsoft caused this with an update. Once I boot into Ubuntu, my first Windows boot after that fails. I reboot another few times and as long as I don't pick Ubuntu in the bootloader screen it boots fine. Recently every time I reboot into Windows after Ubuntu I get a boot failure saying your PC needs to be repaired and that a device required to boot isn't connected.
I've got Ubuntu 14.04 and Windows 8.1 pro dual booting on my PC and everything has been fine until about a month ago.
0 kommentar(er)
