To solve this, double-check that/those files, add it to allowed list or deleted the file then run the backup again.Īfter the next backup attempt, another problem appeared after a while. This error message was related to false positive detection of Windows Defender.
Windows Backup did not complete successfully. The first error message I have received for unsuccessful backup was: When I have configured and run my new backup I have run into an issue (wonders). The reason for this is due to the fact that Windows 10 default backup includes 18 folders that you have to manually remove, one by one, because I like to specify what will be backed up.Īnd here is the old Windows 7 backup that is still present in the latest release of Windows 10.
Even though Windows 10 has a new backup now, I still prefer to use the old Windows 7 backup style. Considering I have just installed Windfrom scratch, this is the first logical thing to do. It returns: DiskPart successfully detached the virtual disk file.After each reinstallation of Windows 10, the first thing to do is to schedule a backup. When you are done retrieving files, and you want to quit, go back to your command prompt window and type DETACH VDISK I was able to retrieve files that I needed by dragging them to the desktop. You can now dig into this drive with your Windows Explorer GUI just the same as any. It returns: DiskPart successfully selected the virtual disk file.Īfter a few secs, your vhd will mount as a new logical drive. Next type SEL VDISK file=”the-location-of-your-file-including-the-file-name”ĭISKPART> SEL VDISK file="J:\WindowsImageBackup\99-DC02\Backup 070031\2a7efb56-0b8e-11e4-8d4c-806e6f6e6963.vhd" It returns a few lines indicating that DiskPart is started. Open command prompt and just type DISKPART I was able to very quickly and easily mount the backup vhd as logical (usable) hard drive by using a built-in Windows program called DISKPART. Now that we are out of that stuck program, we still need to get into the Windows Server Backup vhd.
Super simple: Just go into SERVICES and restart "Block Level Backup Engine." I am not going to answer the question of "What is the underlying problem here?" Because to me the more important questions is, "Is there another (easy) way to achieve my goal? There sure is, and it's built into Windows.įirst, you have to kill off this stuck backup process. My Windows Server Backup program was also stuck forever at "Reading Data Please Wait." (My vhd was saved to a USB-mounted external drive). I was also trying to use Windows Server Backup to mount a recently backed-up vhd.
0 kommentar(er)
