With Vista, Win7, and now Win8, on two different laptops, I’ve had the baffling issue of why Windows Image Backup would not see all of its backups. Since DriveImage was no longer an option, I eventually opted to start using Ghost, but even that had a similar issue: Norton’s Ghost not only does not always see all of its backups, sometimes it doesn’t even see the external drive. So, from Vista through Win7, I started using O&O’s DiskImage, which made fast, reliable and mobile images that could be manipulated the way someone with a mind would want, and I never had a problem. Alas, Windows 8 is a complete nightmare when it comes to images, at least so far, for me, and I have yet to get DiskImage to work properly with it. So, it’s back to WindowsImageBackup.
Being a belt and suspenders guy, I was making backups of backups, and, by accident, I discovered why Windows was not seeing some of the WIB folders: there was an invisible character in the folder name, a non-printing character. I’d been synchronizing some HDDs, and FolderMatch had problems with a Windows Image folder. It wouldn’t synchronize, and it “saw” the name of the folder as “W?indowsImageBackup”. When it kept not synchronizing, I finally pasted the file name into Word, where the ? came out as some kind of symbol that looked like one rectangle inside another. Pressing alt/x gave a code of 200C.
Several of my WIB folders, the ones that Windows never saw, had the same non-printing character added to their file name. It’s hard to have several backups, since Windows will start overwriting them, which it won’t do if you append something such as the date to the folder name. WIB prefers the folder named “WindowsImageBackup”. But I never re-wrote the entire folder name, and even if I wanted to, I’m not sure how or why one would get such a character into a file name. As picky as Windows is about file names, it never occurred to me that you could put such a symbol into a file name.