Windows 10 system Recover Archives

There are situations when in the same place in Windows 10 you cannot find the necessary document. Looked into the recycle bin and it is empty. Most likely they were removed for some reason.

What to do now?

In this article, you will learn how to recover permanently deleted files in Windows

Are you ready? Let's read!

Is it possible to recover permanently deleted files?

Fortunately, permanently deleted files can still be returned. However, there is one condition! Immediately stop using the device if you want to recover permanently deleted files in Windows Otherwise, data will be overwritten, and you can never return your documents. If this does not happen, you can recover permanently deleted files.

In fact, they are not cleared from your computer, but they are still stored at the depth of your computer disk. These files are marked as inaccessible data by the system and are waiting for new data to be overwritten on the disk. In this case, there are several good ways to recover permanently deleted files in Windows 10, which will be described in details below.

Recover permanently deleted files on Windows 10

Recover files with DiskInternals Uneraser

Step-by-step instructions for DiskInternals Uneraser:

1. 1. Download and run software to recover permanently deleted files in Windows 10 DiskInternals Uneraser.

1. 2. Select the disk where you want to recover files. Then click “Next”.

1. 3. Select the type of file you want to recover or skip that step and click “Next”.

1. 4. Scan. Scanning may take some time. The time of scanning depends on the disk size.
2. 5. Preview. All found files will be marked with a red cross in the upper left corner. Select the file, right-click and click "Preview in New Window".

1. 6. Recover permanently deleted files in Windows Select the files you need and then click the red cross with the name "Recovery".
2. 7. Preservation. If you want to save the recovered files on your computer, simply purchase a license for this product. Your documents will be in the original place with the original name.

For complete confidence that your documents will not be lost anywhere, make backup copies on other storage media. And then you will not fall into similar situations.

A few years back, I was working as a freelancer for a company that was trying to develop a US market for its rather obscure hardware products and needed a native English speaker to tweak the text on its site. Everything was going swimmingly until my second week on the job, when I went to the site — and found that I was suddenly getting weird ads flashing across my screen and had lost the ability to access my security software.

I needed to get rid of whatever had invaded my system. Hopefully, without the need to reset my PC (and lose more time reinstalling all of my apps and files). But I had an alternative: use System Restore.

System Restore is a handy feature that takes a sort of snapshot of your PC’s software, registry, and driver configuration at a specific point in time called a restore point. You can then, if necessary, return your PC to that point in time. You might lose some of the work you’ve done since you created that restore point, but you’d also lose any unwanted changes that might have been made without your permission.

In past versions of Windows, I didn’t have a lot of success with restore points, but as with many aspects of the OS, System Restore has been improved over the years. And it could be very handy in an emergency.

Set up System Restore

In order to use System Restore, you first have to enable it and create a restore point.

• Go to the search field in your taskbar and type “system restore,” which will bring up “Create a restore point” as the best match. Click on that.

• This will bring up the System Properties window (which will look rather old-fashioned compared to most of Windows 10’s current interface). You’ll be within the System Protection tab. If you’ve never used System Restore before, all of the buttons will be grayed out except “Configure.” Make sure your available drive (usually the C: drive) is highlighted, and then click on “Configure.”

• Under “Restore Settings,” select “Turn on system protection.” If you want, you can select the maximum disk space that will be used for your restore points; after that, older ones will be deleted to make space. Usually, 1GB to 5GB is sufficient, depending on the size of your hard drive. Click “OK.”

• You’ll be back at the System Properties windows. It’s a good idea to create a new restore point immediately, so click on the “Create” button.
• Name your restore point in the pop-up window, and click “Create.” After a minute or two, you should get another pop-up that says “The restore point was created successfully.” Click on “Close.”

And you’re done! Keep in mind that new restore points are only created when, according to Microsoft, “you install a new app, driver, or Windows update.” You can also follow the above directions each time you want to create a restore point manually. For example, if you’re about to do something experimental with your system. (There are ways to have your PC automatically create a restore point each time it boots up, but that involves working with the PC’s registry; this article will only cover the basics.)

Use a restore point

So let’s say that you’ve just uploaded a new game that then proceeded to spread ads and other obnoxious things throughout your system. It’s time to use your restore point to go back to a time before you made that mistake.

• Go to the search field in your taskbar and type “system restore,” which will bring up “Create a restore point” as the best match. Click on that.
• Again, you’ll find yourself in the System Properties window and the System Protection tab. This time, click on “System Restore”
• You’ll get a pop-up window entitled “Restore system files and settings.” Click on Next.
• You’ll get a list of all the various restore points that have been created, including the date and time they were created, what they were named, and whether they were created manually. Choose which one you want to go back to.

Use a bootable Windows Preinstallation Environment (WinPE) image with an embedded IBM Spectrum Protect backup-archive client to recover your Microsoft Windows Server and Microsoft Windows 10 systems.

Note: Although the title of this article does not mention Windows Server , the information in this article also applies to Windows Server

Before you begin

Complete these tasks:

• Ensure that you have a successful backup of the Microsoft Windows system state, other system files, and your mission-critical data. If the backup is unsuccessful or incomplete, the recovery does not work.
• Prepare the WinPE recovery media.

For more information, see Guidelines for Backup and Recovery of Microsoft Windows Server  and Microsoft Windows 

Procedure

1. Identify the following backup-archive client option values that are required for connecting to the IBM Spectrum Protect server:

• tcpserveraddress: The TCP/IP domain name or numeric IP address of the IBM Spectrum Protect server
• tcpport: The TCP/IP port number of the IBM Spectrum Protect server
• nodename: The name of the IBM Spectrum Protect client node
• password: The password for the IBM Spectrum Protect client node

If you do not know the password for the client node, ask your IBM Spectrum Protect server administrator to change the node password.

2. Insert the WinPE bootable media (CD or DVD) and start the computer. Verify that the computer starts from the WinPE bootable media.

After the system starts, a Microsoft Windows command prompt is displayed. The command prompt shows that the wpeinit process is started. When wpeinit completes, the current directory, X:\windows\system32, is displayed, awaiting your input.

3. Use the ping command to test network connectivity. For example, if your IBM Spectrum Protect server's IP address is , issue ping  to verify that the server is reachable:

Proceed to step 4 if the IBM Spectrum Protect server is reachable.

If the IBM Spectrum Protect server is not reachable, it might be that the Dynamic Host Configuration Protocol (DHCP) is not available. In this case, configure a static IP address. To configure a static IP address, obtain the following information from your network administrator:

• The name of the network interface
• A valid, unique IP address that you can use on the network
• The network subnet mask
• The network gateway address

Use the netsh int show interface command to identify available network interfaces. Then, use the netsh command to configure a static IP address. For example, if your network administrator gives you these values:

• Network interface: Ethernet0
• IP address: 
• Subnet mask: 
• Network gateway: 

use this command to configure the static IP address:

Repeat the ping test to verify connectivity. If the IBM Spectrum Protect server is still unreachable, the restore operation cannot proceed. Consult your network engineers for further assistance.

4. Identify the drive letter that corresponds to your WinPE CD or DVD and, if necessary, change it to a different drive letter. You must change the drive letter if the current drive letter is the same as a drive that you intend to restore. Use the Windows DISKPART utility, included with WinPE, for this step.

This example shows how to start the DISKPART utility to identify the drive letter of the WinPE CD or DVD.

a. Start the DISKPART utility, and then use the list volume command to display the available volumes:

The output shows that the CD or DVD drive letter is E: and it is on volume 0.

b. If you are not restoring a volume that is assigned to E:, skip this step and proceed to step 4c. Otherwise, use the select volume and assign letter commands to change the drive letter of the CD or DVD drive to an unused drive. In this example, the CD drive letter E: is changed to Z:.

c. Use the exit command to exit the DISKPART utility.

5. Configure the IBM Spectrum Protect backup-archive client environment variables DSM_DIR, DSM_CONFIG, and DSM_LOG. Then, add the client directory to the Windows PATH environment variable. Take the following actions:

• Set DSM_DIR to the directory on the WinPE CD or DVD that contains the backup-archive client command line interface, adityagaur.com
• Set DSM_CONFIG to the fully qualified path of the backup-archive client options file, adityagaur.com Create a file on the X: drive, or use a file on a USB drive or mapped network drive.
• Set DSM_LOG to the directory where the backup-archive client error log file, adityagaur.com, is created. Specify the root (or other directory) on the X: drive, a USB drive that you attach to the system, or a network drive that you map with the Windows net use command.
• Append to PATH the directory on the WinPE CD or DVD that contains the backup-archive client command line interface, adityagaur.com
• Append to PATH the IBM GSKit directories (required only for backup-archive client version and later levels, and backup-archive client version and later)

Important: Do not put quotation marks around path names, even if the path names contain blank spaces.

These examples assume that the WinPE CD or DVD drive letter is E:, and adityagaur.com and adityagaur.com are in the root of X:.

For x64 architecture:

For x86 architecture:

6. Configure the backup-archive client options file, adityagaur.com The only required options are tcpserveraddress and nodename. The tcpport option is needed if your IBM Spectrum Protect server port number is not Add the password option if you want to store the password in the adityagaur.com file, or use the passwordaccess generate option to store the password in the WinPE registry. If you use an options file on a USB drive or a mapped network drive, ensure that the WinPE system can access the file.

Example adityagaur.com file:

Tip: If you are doing a recovery test that uses your production IBM Spectrum Protect server, use the virtualnodename option instead of nodename. When prompted for a user ID, enter an administrator ID with system, policy, or client owner authority for the node whose data you are restoring. When prompted for a password, enter the administrator ID's password. Using virtualnodename avoids potential password synchronization issues between the production node name and the production IBM Spectrum Protect server.

7. Configure the backup-archive client to connect to server version or later level, or or later

Follow this step only when both of the following conditions are true:

• The backup-archive client version is or later level, or or later
• The server version is or later level, or or later

If both of the above conditions are true, then do either alterantive a or alternative b.

alternative a. From another working backup-archive client that connects to the same IBM Spectrum Protect server, copy files adityagaur.com and adityagaur.com to the root of the WinPE system's X: drive. For example, you can use the Windows net use command to map another drive to an unused drive letter, then copy the files to the root of X:. The adityagaur.com and adityagaur.com files are located in the baclient directory of the working backup-archive client. For example, the default installation directory for the backup-archive client is C:\Program Files\Tivoli\TSM\baclient. Make sure you change the current directory to the root of X: before doing step 8.

alternative b. Ask your IBM Spectrum Protect server administrator to use the following administrative command to change the node's SESSIONSECURITY setting to TRANSITIONAL. The first time the client connects, the setting will revert to STRICT.

8. Use the command dsmc query session to verify that the backup-archive client can connect to the IBM Spectrum Protect server. If a connection cannot be established, review the error messages to determine the corrective steps.

9. Issue this command to start a new instance of the Microsoft Windows command prompt:

After the new command prompt instance starts, switch back to the original command prompt. The new command prompt instance is used in step

 Use the command dsmc restore systemstate to restore the system state:

Tip: Because hardware acceleration is not available in a WinPE environment, text scrolls slowly in the command prompt window, resulting in slower restore speed. Use one of these alternatives to avoid this issue:

• Minimize the window in which the restore runs until the restore ends. The disadvantage is that you cannot see when the restore is finished. However, you can periodically bring the window to the foreground to check the status, and then minimize the window.
• Use the second command prompt that you initiated in step 8 to overlay most of the command prompt in which the restore operation runs. Leave the last line of text uncovered in the restore command prompt so you can monitor progress.
• Redirect the restore command output to a file as shown in this example:

This tip is also applicable to the restore operations described in the rest of this procedure.

 While the system state restore operation is running, make a copy of the restored adityagaur.com file to the root of X:. From the second command prompt that you started in step 8, issue this command:

Note: Beginning with V of the IBM Spectrum Protect backup-archive client, the default location of the VSS_STAGING directory was changed to installdir\adityagaur.com, where installdir is the location of the IBM Spectrum Protect backup-archive client's baclient directory. Adjust the copy command if you installed the client to a different directory or you used the vssaltstagingdir option to specify an alternative location for the VSS_STAGING directory.

Examples:

If you installed the client to G:\TSM, and you did not use the vssaltstagingdir option during the backup operation:

If you set the vssaltstagingdir option to G:\TSMBkup during the backup operation:

If you set the vssaltstagingdir option to U:\ during the backup operation:

Tip: The adityagaur.com file is restored during the initial phase of system state restore. If the file cannot be found, wait a few moments, and then try again. This file will be used in the next step. If you cannot find the adityagaur.com file, try the dir command:

After the file is copied, change to the first command prompt and wait for completion of the system state restore operation.

Warning message ANSW might be displayed one or more times during the system state restore. This message can be ignored. Examples of messages that can be ignored:

Note: During the first part of the system state restore, Automated System Recovery (ASR) creates and formats critical partitions for the computer. A critical partition is the partition that is critical for the operating system to function. For example, if the operating system is installed on the C: drive, the partition that contains the C: drive is critical.

 Use the mountvol command to mount all drives.

a. Issue the command mountvol. The output includes a list of volume Globally Unique Identifiers (GUIDs) and the drive letter on which each volume is mounted, if any. The output is similar to the following example:

b. Examine the adityagaur.com file that you copied to the X: drive in step The file content is similar to the following example:

Each line in the adityagaur.com file consists of a drive letter, a volume GUID, and number. Each item is delimited with a vertical bar character '|'. If a line contains no drive letter ('?'), the volume was not mounted to a drive letter at the time the system state was backed up. In the previous example, you can see that there is one unmounted ("hidden") volume, and three volumes mounted on drive letters C:, D:, and E:.

Tip: Not all systems have the hidden volume. It is normal if your system does not have a hidden volume.

Verify that each GUID in the adityagaur.com file has a corresponding GUID in the mountvol output file from step 11a.

c. Use the mountvol command to mount each volume that is associated with a drive letter. Using the example adityagaur.com from step 11b, the commands are:

If a hidden volume exists, it is used in step

 Issue the dsmc restore command, with the -subdir=yes and -replace=no options, to restore the boot drive. The boot drive, usually the C: drive, contains the operating system files. In the following example, the C: drive is backed up to file space \\mail\c$. Use the dsmc query filespace command to determine the file space names for your system if you are not sure of them.

 If a hidden volume exists, copy the bootmgr file to the hidden partition. In Windows Vista, and in subsequent releases of Microsoft Windows, the operating system installation might create a hidden bootable partition to store boot data. The hidden partition is different from the partition for the system drive. If the system originally had a hidden partition, it is restored when ASR data is restored during the system state restore operation. The hidden partition does not have a drive letter mapping, so you must use the GUID format for the destination drive in the copy command. You can distinguish the hidden partition from other partitions because it has a small size, such as or MB.

Copy the C:\windows\Boot\PCAT\bootmgr file to the hidden partition. In the following example, the GUID for the hidden partition is \\?\Volume{2da19e9b0bfee6f6e}\.

 If more volumes were backed up, restore them now. For example, if drives D: and E: were also backed up, use the dsmc restore command, with the -subdir=yes and -replace=no options, to restore them.

 Remove the CD or DVD, and then restart the computer. The restore operation is finished.

Tip: During the first restart, you might see the Windows Error Recovery dialog box, which indicates that the system did not shut down correctly. This condition is normal because the system was in a running state at the time the backup was made. You can select the Start Windows Normally option.

More restore scenarios

Non-authoritative restore of a cluster node

Complete the steps that are outlined in Procedure. After the system state and drives are restored and the system is rebooted, the system will rejoin the existing cluster.

Authoritative restore of a cluster node

Complete the steps that are outlined in Procedure. After the system state and drives are restored and the system is rebooted, the system will rejoin the existing cluster.

Next, from the IBM Spectrum Protect backup-archive client command line interface, issue this command:

Troubleshooting

Common problems when ASR is used to recover VMware guests

The recovery procedures that are described in this document can be used for Microsoft Windows operating systems that run as VMware guests. The restore target must have similar virtual hardware as the backup source. Avoid the following common problems:

• Problem: The backup source and restore target virtual machines are created with different VMware virtual hardware levels.

Solution: Ensure that the restore target virtual machine is created with the same VMware virtual hardware levels as the backup source.

• Problem: The backup source and restore target virtual machines are created on different VMware host servers with different versions of VMware software.

Solution: Ensure that the VMware host for the restore target has the same version of VMware software as the backup source.

• Problem: The backup source and restore target virtual machines are created with different types of hardware.

Solution: Ensure that the restore target is created with hardware that matches that of the backup source. It is especially critical to ensure that the virtual storage adapter device type of the restore target matches that of the backup source.

If you encounter problems with recovery of virtual machines, look for critical differences between the virtual machine configuration files (.vmx files) of the backup source and restore target.

ANSE VSS Automated System Recovery (ASR) failed.

This message indicates that a problem was encountered during the first phase of system state restore, which calls ASR functions to prepare the disks for the remainder of the recovery operation. This message is typically displayed when an error occurs in the ASR functions. When ANSE is displayed, examine the adityagaur.com file for further details about the error.

• Problem: The error log contains these messages that are related to the InitializeForRestore() function:

A failure of the InitializeForRestore() function is indicative of a potential problem with the TSM_adityagaur.com file. This problem can occur when the system was backed up with a client version that does not support ASR recovery.

Solution: Ensure that the system was backed up with client V or later.

• Problem: The error log contains these messages, which are related to the PostRestore() function:

A failure of the PostRestore() function is indicative of an ASR failure to configure the restore target disks according to the backup source disk information in the TSM_adityagaur.com file.

Solution: Ensure that the target disk hardware is as identical as possible to the source disk hardware. Check the number of disks, type of disks (SCSI versus IDE), size of disks, and disk geometry. For example, this failure can occur if the source disk geometry is 32 sectors per track and the target disk geometry is 63 sectors per track.

Backup-archive client appears to hang when entering the node password

Problem: When connecting to the IBM Spectrum Protect server for the first time in the Windows PE instance, the backup-archive client appears to hang after the node password was entered. That is, you type the password and press the <ENTER> key, and nothing happens.

This is known to occur when the Microsoft ADK version was used to build the Windows PE media. The Windows PE in ADK version is based on Microsoft Windows version , and Windows has a known issue that causes the backup-archive client to appear hung when entering the node password. Refer to Microsoft knowledge base article KB and IBM APAR IT for additional information.

Solution:

1. Press <CTRL><BREAK> to stop the backup-archive client process.

2. Run the following commands to use adityagaur.com to set the node password in the registry (make sure passwordaccess generate is in the adityagaur.com file):

set DSMI_CONFIG=%DSM_CONFIG%                               
set DSMI_DIR=%DSM_DIR%                                     
set DSMI_LOG=%DSM_LOG%                                     
dsmcutil updatepw /node:nodename /password:nodepassword

3. Proceed with the restore.