backup-.png You have insufficient rights to see the content.

Backup of C drive only but fails 0x00070015 - what is this?

---

When I try and and do a Disk2VHD with shadow cop, it fails - is this the problem? Is it a matter of enabling shadow copy?

---

Hang on - my 4TB disk says that it is an MBR disk even though I am using 3.722TB

---

Tried a new disk with no changes - what happened to the option where backup took control of the disk and did the backup? It just doesn't seem to work properly anymore!

---

can I backup windows 11 with the windows 7 utility?

---

Yes, you can use the "Backup and Restore (Windows 7)" utility in Windows 11 to create backups. This utility is still included in Windows 11, even though it's a legacy tool originally designed for Windows 7. However, there are some important things to keep in mind:
1. Limited Features Compared to Modern Tools

The "Backup and Restore (Windows 7)" utility lacks some of the advanced features found in more modern backup solutions, such as File History or third-party tools. It's designed primarily for creating system images and backing up files.

2. Creating a System Image Backup

You can use the utility to create a full system image of your Windows 11 installation. This will include all system files, installed programs, and user data.
To do this:
Open the Control Panel and go to System and Security.
Click on Backup and Restore (Windows 7).
Select Create a system image from the left-hand menu.
Choose where to save the backup (an external hard drive is recommended).
Follow the prompts to complete the backup process.



3. Backing Up Files

You can also use this utility to back up specific files or libraries.
To set up a file backup:
Open Backup and Restore (Windows 7) from the Control Panel.
Click on Set up backup.
Choose where to save your backup and select the files or libraries you want to include.
Schedule the backup if needed, then let the process complete.



4. Compatibility with Windows 11

While the tool works on Windows 11, it’s important to note that it’s no longer actively developed or supported for new features by Microsoft. It works, but it might not be as reliable or efficient as newer tools.
You might encounter issues with restoring backups made on Windows 11 if you try to restore them on future versions of Windows, especially as this tool may be deprecated in future Windows updates.

5. Consider Modern Alternatives

File History: This is the more modern backup tool in Windows 10 and 11. It continuously backs up versions of your files stored in Documents, Music, Pictures, Videos, and Desktop folders, and you can restore them if needed.
Third-Party Backup Solutions: Tools like Acronis True Image, Macrium Reflect, or EaseUS Todo Backup offer more features and are updated to work with the latest versions of Windows.

Conclusion
While you can use the "Backup and Restore (Windows 7)" utility in Windows 11, it’s advisable to consider more modern alternatives for better reliability, features, and future compatibility. If you prefer the old tool for its simplicity or familiarity, it should serve basic backup needs adequately.

---

I cannot make it work - it fails instantly

---

If the "Backup and Restore (Windows 7)" utility fails instantly when you try to create a backup on Windows 11, here are some steps you can take to troubleshoot and potentially resolve the issue:
1. Check for Windows Updates

Ensure that your Windows 11 installation is fully updated. Sometimes, issues with built-in utilities are resolved through updates.
Go to Settings > Windows Update and check for updates.

2. Run the Backup Troubleshooter

Windows has a built-in troubleshooter that might help diagnose and fix issues with the backup utility.
Open Settings > System > Troubleshoot > Other troubleshooters.
Look for the Backup and Restore troubleshooter (if available) and run it.

3. Check Disk Space

Make sure there is enough free space on the destination drive where you're trying to save the backup.
Also, check the drive for errors using the following steps:
Open File Explorer and right-click the drive you want to check.
Select Properties > Tools.
Under Error checking, click Check and follow the prompts.



4. Run CHKDSK

Sometimes, disk errors can cause backup failures. Running CHKDSK (Check Disk) might help:
Open Command Prompt as an administrator by searching for "cmd" in the Start menu, right-clicking on Command Prompt, and selecting Run as administrator.
Type chkdsk /f /r and press Enter.
You may need to restart your computer to allow the check to complete.



5. Check Backup Service Status

Ensure that the Windows Backup service is running:
Press Win + R, type services.msc, and press Enter.
Find Windows Backup in the list.
Right-click on it, and make sure it is set to Automatic. If it's not running, start it.



6. Clear Previous Backup Configurations

Corrupted or incomplete previous backups might cause issues.
Go to Control Panel > System and Security > Backup and Restore (Windows 7).
Click on Manage Space and then View backups. Delete any old or incomplete backups.

7. Use an Alternative Backup Solution

If the built-in tool continues to fail, consider using a third-party backup solution. Macrium Reflect, Acronis True Image, and EaseUS Todo Backup are popular options that offer more features and reliability.

8. Check Event Viewer for Errors

If the backup fails instantly, checking the Event Viewer might provide more detailed error messages:
Press Win + X and select Event Viewer.
Go to Windows Logs > Application and System to look for errors related to the backup process.
You can search for the specific error code or message to find more targeted solutions.



If you go through these steps and the issue persists, it might be an underlying compatibility or system configuration problem. At that point, using a modern backup tool might be the best solution.

---

when i try using disk2vhd it cannot snapshot teh volumes

---

When using Disk2vhd and encountering issues where it cannot snapshot the volumes, this is usually related to certain conditions on the system that prevent the creation of the Volume Shadow Copy (VSS) snapshot, which Disk2vhd relies on to create the virtual hard disk (VHD) file. Here are steps you can take to troubleshoot and resolve this issue:
1. Check Volume Shadow Copy Service (VSS)

Disk2vhd requires the Volume Shadow Copy service to create a consistent snapshot of the volume. Ensure that this service is running:
Press Win + R, type services.msc, and press Enter.
Find Volume Shadow Copy in the list of services.
Make sure the service is started and set to Manual or Automatic. If it’s stopped, start it.



2. Ensure Sufficient Disk Space

VSS requires free disk space on the volumes being snapped, as well as on the system volume where the snapshot is temporarily stored.
Make sure there is adequate free space on all involved volumes, especially the system drive (usually C:).

3. Check for Disk Errors

Disk errors can prevent snapshots from being taken. Run CHKDSK on the volumes you’re trying to snapshot:
Open Command Prompt as an administrator.
Type chkdsk /f /r followed by the drive letter (e.g., chkdsk C: /f /r) and press Enter.
Allow the scan to complete, and then try Disk2vhd again.



4. Check Event Viewer for VSS Errors

VSS-related errors are often logged in the Event Viewer:
Press Win + X and select Event Viewer.
Navigate to Windows Logs > Application.
Look for errors related to VSS or Disk2vhd and review the details.


Common VSS errors include issues with writers, storage, or the service itself. Specific error codes can help in finding more targeted solutions.

5. Restart the VSS Service

Restarting the Volume Shadow Copy service can sometimes clear issues:
Open Services (via services.msc).
Right-click Volume Shadow Copy and select Restart.



6. Update Disk2vhd

Ensure you are using the latest version of Disk2vhd, as older versions might have bugs or compatibility issues with newer Windows versions.
Download the latest version from the official Microsoft Sysinternals website.

7. Check for Conflicting Software

Certain third-party applications like antivirus programs or disk utilities might interfere with VSS. Temporarily disable these programs and try running Disk2vhd again.

8. Create a Manual VSS Snapshot

You can manually create a VSS snapshot to check if the process works outside of Disk2vhd:
Open Command Prompt as an administrator.
Run vssadmin create shadow /for=C: (replace C: with the relevant drive letter).
If this fails, it will provide more specific error messages related to VSS.



9. Consider Running in Safe Mode

Running Disk2vhd in Safe Mode can sometimes bypass issues caused by other software or services running in the background:
Restart your computer in Safe Mode.
Run Disk2vhd and attempt to create the snapshot.



10. Use Another Tool or Method

If Disk2vhd continues to fail, you might consider using another tool like Sysinternals' Disk2vhd alternatives, or third-party VHD creation tools such as Acronis True Image or Macrium Reflect, which may handle volume snapshots differently.

If after trying these steps you still can't get Disk2vhd to work, there might be a deeper underlying issue with the system's ability to create VSS snapshots that may require further investigation or a different approach for creating a VHD of your system.

---

Does Windows 7 Backup use VSS to make the backup?

---

Yes, Windows 7 Backup does use the Volume Shadow Copy Service (VSS) to create backups. VSS is essential for creating consistent backups of files that may be in use or locked by the operating system. Here's how it works:
How VSS Works in Windows 7 Backup:

VSS Snapshots: When you initiate a backup in Windows 7, the system uses VSS to create a snapshot of the entire volume. This snapshot captures the state of the files at a specific point in time, allowing the backup utility to copy files even if they are currently in use.
Consistency: VSS ensures that the files are consistent, particularly with databases or other applications that may be writing data while the backup is running.
System Image Backups: If you choose to create a system image, VSS is used to capture a complete image of the drive, ensuring that all system files, installed programs, and user data are accurately backed up.

Troubleshooting VSS Issues with Windows 7 Backup:
If the backup is failing or encountering issues, it could be due to problems with VSS. Common issues include:

VSS Service Not Running: The Volume Shadow Copy service must be running for backups to work.
Insufficient Disk Space: VSS requires free space on the volume being backed up, as well as the volume where the shadow copy is stored.
VSS Writer Errors: Specific VSS writers (components of VSS that handle different types of data) might fail, causing the backup to fail. You can check the status of VSS writers using the vssadmin list writers command in the Command Prompt.
Disk Errors: Corrupt or damaged sectors on the disk can prevent VSS from successfully creating a snapshot.

Conclusion
If you encounter backup issues, checking the VSS service, ensuring there’s enough disk space, and reviewing the Event Viewer logs for VSS-related errors can help diagnose and resolve the problem.

---

So these two problems most likely have the same root - where do I check on volume shadow copy and enable/disable it in Windows 7?

---

Yes, it's quite possible that the issues with both Windows 7 Backup and Disk2vhd are related to problems with the Volume Shadow Copy Service (VSS). Here's how you can check the status of VSS, enable or disable it, and troubleshoot any issues in Windows 7:
1. Check the Volume Shadow Copy Service (VSS) Status
Via Services Manager:

Open the Services Manager:

Press Win + R to open the Run dialog box.
Type services.msc and press Enter.


Locate the Volume Shadow Copy service:

In the Services window, scroll down to find Volume Shadow Copy.


Check the Status:

The Status column should indicate whether the service is Running.
The Startup Type should be set to Manual (this is the default setting, which means it starts when needed).


Start the Service if It's Not Running:

If the service is not running, right-click on Volume Shadow Copy and select Start.
If you want to make sure it always starts automatically, you can right-click, select Properties, and set the Startup type to Automatic.



Via Command Prompt:

Open Command Prompt as Administrator:

Search for cmd in the Start menu, right-click on Command Prompt, and select Run as administrator.


Check the VSS Service Status:

Type the following command and press Enter:sc query vss


This will display the current status of the Volume Shadow Copy service.


Start the VSS Service:

If the service is not running, you can start it by typing:net start vss





2. Check and Manage VSS Storage (Shadow Copies)
If VSS is running but you're still having issues, it may be related to storage settings for shadow copies.
Check Shadow Copy Storage:

Open Command Prompt as Administrator.
Check VSS storage configuration:
Type the following command and press Enter:vssadmin list shadowstorage


This will display the allocated, used, and maximum size of the storage space used for VSS snapshots.



Adjust or Delete Existing Shadow Copies:
If there's insufficient space or other issues with shadow copies, you can adjust the storage size or delete old snapshots.

Resize the Shadow Storage:

Use the following command to resize the storage space:vssadmin resize shadowstorage /for=C: /on=C: /maxsize=XXGB


Replace C: with the appropriate drive letter and XXGB with the amount of space you want to allocate.


Delete Old Shadow Copies:

If needed, you can delete existing shadow copies to free up space:vssadmin delete shadows /for=C: /oldest


This command deletes the oldest shadow copy on the specified drive (replace C: with the correct drive letter).



3. Check VSS Writers
VSS writers are responsible for ensuring that data is correctly written to the shadow copies. If a VSS writer is failing, it can cause the backup process to fail.

List All VSS Writers:
In the Command Prompt (as administrator), type:vssadmin list writers


This will display a list of VSS writers and their current status. If any writers are listed with errors, this could be the source of the problem.



4. Restart VSS Service
Sometimes simply restarting the VSS service can resolve transient issues.

Restart the Service:
Go to the Services Manager (services.msc).
Right-click Volume Shadow Copy and select Restart.



5. Check Event Viewer for VSS Errors
If the above steps do not resolve the issue, check the Event Viewer for specific VSS errors.

Open Event Viewer:

Press Win + X and select Event Viewer.


Navigate to VSS Logs:

Go to Windows Logs > Application.
Look for entries related to VSS. Any errors or warnings here can provide more detailed information on what's going wrong.



By following these steps, you should be able to diagnose and potentially resolve the VSS issues that are preventing both Windows 7 Backup and Disk2vhd from working correctly.

---

I am seeing:

---

The output you’ve provided indicates that two of the Volume Shadow Copy Service (VSS) writers, specifically the WMI Writer and the MSSearch Service Writer, are in a [7] Failed state with a Last error: Timed out. These errors can cause issues with backups and other processes that rely on VSS, like Disk2vhd.
Steps to Troubleshoot and Resolve VSS Writer Issues
1. Restart the VSS Writers

Restarting the affected services associated with these writers can sometimes clear the issue.

For the WMI Writer:

Press Win + R, type services.msc, and press Enter.
Find the Windows Management Instrumentation service.
Right-click on it and select Restart.

For the MSSearch Service Writer:

In the same Services window, find the Windows Search service.
Right-click on it and select Restart.

After restarting these services, run the vssadmin list writers command again to check if the writers have returned to a [1] Stable state.
2. Restart the VSS Service

Restarting the Volume Shadow Copy service itself can also resolve writer issues:
In the Services Manager (services.msc), find Volume Shadow Copy.
Right-click on it and select Restart.



3. Check for Disk Space Issues

Ensure that there’s sufficient disk space on the system and the volumes you're trying to snapshot. Lack of space can lead to VSS timeouts.

4. Check for Disk Errors

Run CHKDSK on the affected volumes to ensure there are no disk errors causing the timeouts:
Open Command Prompt as an administrator.
Type chkdsk C: /f /r (replace C: with the appropriate drive letter) and press Enter.
Allow the disk check to complete and then try the VSS process again.



5. Increase Shadow Copy Storage Space

Sometimes, increasing the allocated space for shadow copies can help:
Open Command Prompt as an administrator.
Run the following command to increase the shadow storage:vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10%




Replace C: with the appropriate drive letter and adjust the size (10% or XXGB) as needed.



6. Re-register VSS Components

If the issues persist, re-registering the VSS components can sometimes resolve deeper issues:
Open Command Prompt as an administrator.
Run the following commands one by one:regsvr32 /s vssvc.dll
regsvr32 /s swprv.dll
regsvr32 /s eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll


After completing these, restart your computer.



7. Check Event Viewer for Specific Errors

Review the Event Viewer for more detailed error messages related to these timeouts, which can sometimes give you more specific guidance on what’s causing the issue.
Open Event Viewer (Win + X > Event Viewer).
Look under Windows Logs > Application and System for any VSS or service-related errors.



Final Steps
After performing these steps, recheck the status of the VSS writers using vssadmin list writers. If the writers are now stable, you should be able to proceed with using Windows 7 Backup or Disk2vhd without issues.
If the errors persist even after trying these steps, there may be deeper system issues at play, and you might need to consider more comprehensive system diagnostics or consult with a professional for further troubleshooting.

---

The problem seems to be that it cannot snapshot the recovery sector of the system disk - it can snapshot the EFI and C: drive but not the recovery sector of 622 MB on the same disk

---

If the issue is that the Volume Shadow Copy Service (VSS) cannot snapshot the recovery partition on your system disk, there are a few specific considerations and steps you can take to address this:
1. Recovery Partition Limitations

The recovery partition is a special partition used for restoring the system to its factory state or performing other recovery operations. It typically doesn’t contain user-accessible files and is often hidden.
VSS may struggle with such partitions because they are not typically meant to be included in backups or VHD snapshots.

2. Exclude the Recovery Partition from Backup or Snapshot

Since the recovery partition is usually not necessary for system backups (as it's primarily for factory resets), you can try excluding it from the backup or snapshot process.

Using Disk2vhd:

When selecting volumes to include in the snapshot, deselect the recovery partition (usually marked as a small, hidden partition) and only select the EFI and C: drive.

Using Windows 7 Backup:

Unfortunately, Windows 7 Backup doesn't provide an option to exclude specific partitions directly. However, you can still create a system image that excludes non-essential partitions by using custom backup tools or third-party software.

3. Check the Recovery Partition

Ensure that the recovery partition is not corrupted, as corruption might prevent VSS from creating a snapshot.

Check the Partition for Errors:

Open Command Prompt as Administrator.
Run CHKDSK:
You can attempt to run chkdsk on the recovery partition, but be aware that accessing it directly might be restricted:chkdsk 😨 /f /r


Replace 😨 with the drive letter assigned to the recovery partition if it has one (if it doesn’t, you might need to temporarily assign a drive letter using Disk Management).



4. Use Disk Management to Analyze the Partition

Open Disk Management to view the recovery partition's status and see if there are any issues or if it’s mounted correctly.

Steps:

Press Win + X and select Disk Management.
Look for the Recovery Partition:
Check if the partition is healthy and see if it’s marked as active or hidden.


Assign a Temporary Drive Letter:
Right-click the recovery partition and choose Change Drive Letter and Paths. Assign a temporary drive letter if one is not already assigned. After checking, remove the drive letter to prevent unintended access.



5. Use Third-Party Backup Tools

If excluding the partition or troubleshooting doesn’t resolve the issue, consider using a third-party tool like Macrium Reflect or Acronis True Image. These tools often handle partitions more flexibly and may allow you to exclude or manage the recovery partition more effectively.

6. Create a Custom System Image

If you absolutely need to include the recovery partition in your backup, consider creating a custom system image using DISM (Deployment Imaging Service and Management Tool) or similar command-line tools. However, this process is more advanced and typically used by IT professionals.

7. Consider Rebuilding the Recovery Partition

If the recovery partition is corrupted and you need it, consider rebuilding or repairing it using the Windows installation media. This process is complex and should be done with caution, as it may affect your ability to perform factory resets.

Final Steps

If excluding the recovery partition from the backup is acceptable, this is the simplest and most straightforward solution.
If the recovery partition is necessary for your backup strategy, you may need to explore more advanced options or tools to handle it appropriately.

If these steps don't resolve the issue, further investigation into the specifics of your system configuration and possibly consulting with a professional might be necessary.

---

I finally deleted the recovery partitions which was showing up as RAW in DISKPART anyway and now the backup is working fine.

---

It sounds like deleting the recovery partition that was showing up as RAW has resolved the issue, and now your backup is working fine. That makes sense, as a RAW partition usually indicates that the file system is corrupted or unrecognized, which can indeed cause problems with backup tools trying to snapshot or include it.
Key Takeaways:

RAW Partitions:

RAW status generally means that the partition is unreadable by the operating system, likely due to corruption. Backup tools like Windows 7 Backup or Disk2vhd may fail when they encounter such partitions because they cannot properly access or snapshot the data.


Deleting Problematic Partitions:

By deleting the problematic recovery partition, you've removed the source of the conflict, allowing the backup process to complete without errors.


Backup Now Working:

With the RAW partition removed, the Volume Shadow Copy Service (VSS) can now successfully create snapshots of the remaining volumes, enabling the backup to proceed smoothly.



What to Do Next:

Ensure You Have a Recovery Plan: Since the recovery partition was deleted, it's a good idea to ensure you have an alternative recovery plan in place. This could include:

Creating a recovery drive using a USB stick via the Recovery Drive tool in Windows 11.
Keeping a system image backup in a safe location.
Having access to Windows installation media to perform repairs or reinstall if needed.


Monitor Backup Integrity: Now that the backup is working, periodically check that your backups are completing successfully and test restore capabilities if possible to ensure that your data is being backed up correctly.


If you have any further questions or need assistance with anything else, feel free to ask!

---