How to Fix Backup Error 0x80070002

If you suddenly find the Windows Recovery Environment not working and you see an error message saying, “Could not find the recovery environment”, then you’ve come to the right place as this post will guide you on how you can fix it. In times when you can’t boot into the Windows Recovery Environment, there could be several reasons behind it. However, have you ever wondered where exactly the Windows Recovery Environment is in your computer? Windows initially places the Windows RE Image file in the installation partition during Windows Setup so if you have installed Windows in the C drive, you can find the Windows RE at the C:/Windows/System32/Recovery or C:/Recovery folder. Keep in mind that this folder is hidden and later on, the system copies the image file into the recovery tools partition to make sure that one can boot into recovery if there are any issues with the drive partition. The “Could not find the recovery environment” error mostly occurs if the Windows Recovery Environment is disabled or if the “Winre.wim” file is corrupted. Thus, to fix this error, you need to refer to the given suggestions below.

Option 1 – Try to enable Windows Recovery Environment

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• Next, type the “reagentc /info” command and tap Enter to execute it.
• After that, if the output states that Status is enabled, then you’re all set.
• Now type the “reagentc /enable” command and tap Enter to enable the Windows Recovery Environment. You will see a success message at the end signifying that Windows RE is available.

Option 2 – Try to fix the corrupted or missing “Winre.wim” file

If the Winre.wim file is either corrupted or missing, you need to get a new copy of this file from another computer where the Windows RE is working. Once you’re able to get a new copy of the Winre.wim file, you have to set the image path to a new location. For more details, refer to these steps:

• First, type “Powershell” in Windows Start Search and right-click on Windows PowerShell from the results, and select Run as administrator.
• Next, execute the given command below to change the path of the WIM file to the new location. Note that the steps should be used when the file path of the Windows Recovery Environment is different from the usual spot.

Reagentc /setreimage /path C:RecoveryWindowsRE

• As mentioned, if the file is corrupted, you just have to get a new copy from another PC but before you do that, make sure that the WINRE on that computer is disabled (just enable it later on) and then place it in the C:/Recovery path and then set its path again using the command given above and then verify its path by executing the following command.

reagentc /info command

Note: Since the Recovery folder is hidden as well as the WINRE folder in it and you won’t be able to access them using the Windows File Explorer, you need to use the Windows PowerShell or Command Prompt so that you can access them.

Option 3 – Try checking and fixing the WinRE Reference in the Windows Boot Loader

The Windows Boot Loader is the one that determines if it has to load the Windows Recovery Environment. It could be that the boot loader is pointing to an incorrect location which is why you’re getting the error. To resolve it, you have to check and fix the WinRE Reference in the boot loader. How? Follow these steps:

• In the Windows Start Search, type “PowerShell” and from the search results that appear, right-click on Windows PowerShell and then select the “Run as administrator” option to open it with admin privileges.
• After that, execute the “bcdedit /enum all” command.
• Next, look for an entry in the Windows Boot Loader identifier set as Current and look for “recoverysequence” in that section and take note of the GUID.
• Ensure that the device and the osdevice items show the path for the Winre.wim file and that they are the same. If not, you need to point the current identifier to the one which has the same.
• Once you’ve found the new GUID, execute this command: bcdedit /set {current} recoverysequence {GUID_which_has_same_path_of_device_and_device}
• Now check if the error in the Recovery Environment is fixed or not.

Option 4 – Try creating a Recovery Media

You could also try creating a Recovery Media to resolve the error in the Windows RE. All you have to do is download the Windows 10 ISO file using the Media Creation tool and then create a recovery drive. Once you’re done, check if it fixes the problem or not.

If you are using a couple of graphics-intensive applications like video rendering software or some games, then something in the background of the system could get messed up and you might encounter the “LoadLibrary failed with error 1114, A dynamic link library (DLL) initialization routine failed” error message. This kind of error can usually get fixed by twerking some graphic settings, fixing and updating the drivers, and allowing your PC to work by leveraging the maximum use of the resources it’s got. Thus, in this post, you will be guided on some measures you can apply to resolve this kind of error message as soon as possible. Before you go over the options given below, if you have made any changes to any software component in your computer or installed new software recently, then you might want to undo them and then check if it fixes the “LoadLibrary failed with error 1114 “ error. Once you have that covered but you’re still getting the error, use the options given below as a reference to fix the error.

Option 1 – Try to modify the Dynamic Graphics Settings

You might want to modify the Dynamic Graphics Settings in order to fix the error. To do so, follow the steps below.

• Open Control Panel and then Power Options.
• From there, click on the Change plan settings option for your chosen power plan.
• After that, click on Change advanced power settings.
• Then look for the Switchable Dynamic Graphics option and then click on it to expand it.
• Afterward, expand the Global Settings option and then select Maximize Performance for both the “On battery” and “Plugged in” options.
• Now click on the Apply button and then OK to save the changes made.

Note: If the Switchable Dynamic Graphics option is not available on your computer, you can try the next given option below.

Option 2 – Try switching the Graphics card to High-Performance mode

Note that this second option varies from computer to computer since most computers use the Graphics card made by NVIDIA, while some by AMD and others use Intel HD Graphics. Thus, depending on which graphics card your computer uses, pick one of the three fixes below.

NVIDIA Graphics Drivers:

If your computer uses a graphics card made by NVIDIA and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop and then click on the NVIDIA Control Panel.
• After that, expand the 3D Settings on the left-hand side tree-structured list and then click on Manage 3D Settings.
• Next, select your preferred GPU on the right-side panel and then set it to the High-Performance NVIDIA Card from the drop-down menu.
• As an alternative, you can also go to the Program Settings tab,
• From there, select the program that you are trying to run from the drop-down menu and click on Add.
• Now set the graphics processor to a High-performing processor and then restart your computer to apply the changes made.

AMD Graphics card:

If your computer uses a graphics card made by AMD and has the drivers are properly installed and updated, then follow the steps below.

• Right-click on any empty space on your desktop.
• Click on AMD Control or Configure Switchable Graphics.
• Next, click on Browse and select the program where you encounter the error.
• Finally, click on High Performance for the selected program and then restart your computer to successfully apply the changes made.

Intel HD graphics:

If your computer uses the Intel HD graphics and then its drivers are properly installed and updated, then follow these steps:

• Right-click on any empty space on your desktop and then click on the Intel Graphics Settings.
• Next, click on the Power menu.
• After that, select a Graphics Power Plan for both the “On battery” and “Plugged in” options to High-Performance Power Plan.
• Then click on the Apply button and restart your computer.

A lot of users prefer to use Microsoft OneDrive when it comes down to cloud storage as it does not only come with the seal of approval from Microsoft but it’s also primarily good and better compared to other cloud storage services. However, that doesn’t mean that OneDrive isn’t without any issues. For one, you might encounter an issue where the OneDrive thumbnails do not show in File Explorer in Windows 10. If you are currently experiencing this problem, read on as this post will help you fix it. As you know, you can add OneDrive to your Windows 10 computer and have all the files locally synchronize to the cloud and so on. This means that whatever is available in the cloud will be seen on your computer. It is smooth and definitely saves you a lot of time which is why a lot of users prefer to use it. So if you suddenly not see any thumbnails in OneDrive, then that would be a problem. You are actually not the only one having this problem as there are other users who reported getting the same issue recently about the picture thumbnails that no longer show up in the OneDrive folders in the File Explorer. At the time of writing, it isn’t clear yet what the cause of the issue really is. Even so, there are still potential fixes you can check out to resolve it, and the sooner you do it, the better as this can be a major problem. To get started, refer to the instructions given below.

Option 1 – Try to disable Files on Demand

The first thing you can do to fix the problem is to disable the Files on Demand. This is what you have to do to get things under control.

• First, right-click on the OneDrive icon located in the taskbar and go-to of OneDrive.
• After that, click on More and Settings. This will open a new window where you have to click on the Settings tab and uncheck the “Files on Demand” service.
• Once done, restart your computer and check if you can now see the thumbnails in the OneDrive folder. However, if it didn’t work, then proceed to the next given option below.

Option 2 – Try to change the icon view

The next thing you can do to fix the problem is to change the icon view. It is possible that the problem might have something to do with the size of the icons than anything else. So you have to change the icon view and to do that, follow these steps:

• First, open Control Panel in Windows 10.
• Next, in the search box, type “folder” and then click on the File Explorer Options.
• From there, click on the View tab and uncheck the “Always show icons” option, and make sure that showing thumbnails is active.
• Now go back to Control Panel and type “system” in the search box. This will open a new window where you have to select the “View advanced system settings” option.
• Then under the Performance section, click on Settings and click on the option that allows you to show the thumbnails instead of icons.

Stop C00002lA Fatal System Error- What is it?

C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down. The stop C000021A error message is displayed in the following format:

Stop c000021a {Fatal System Error} The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.

Error Causes

The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen. Here are some of the underlying causes for the stop C0000021A error:

• The incompatible third-party program
• Hard disk issues
• Service pack installation has failed
• Mismatched system files have been installed
• Bad and invalid registry keys

Further Information and Manual Repair

To resolve the stop C000021A Fatal System Error on your PC try the following solutions:

• Remove Incompatible Third Party Programs

If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program. To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list. Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.

• Repair and Restore the Registry

This procedure is slightly long and tricky. To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT. Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive. Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST. Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1. This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002. Now locate the following registry key: HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open. Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys: HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation. This will resolve the stop C000021A error.

If you suddenly find the middle mouse button not working as you use it on your Windows 10 computer, then you’ve come to the right place as this post will provide some suggestions that can help you fix the issue. This kind of problem can affect your experience in using your computer as the middle mouse button helps you in scrolling through long web pages and screens with a lot of data. So if that stops, you will end up using your keyboard instead which is kind of a hassle compared to using the middle mouse button. It is possible that this problem could have something to do with either the hardware or software. To isolate the possibility of a hardware failure, you can try to connect the mouse to a different computer and see if it works just fine there or if it still has the same problem. If the mouse works properly on a different computer, then the issue is software-related. It is possible that a software update, especially gaming software, could have been misconfigured in a way that the middle button does not respond like it’s supposed to. To resolve the problem, you might want to try reinstalling or updating the mouse drivers or run the Hardware and Devices troubleshooter. You can also install OEM-specific mouse drivers or modify some entries in the Windows Registry.

Option 1 – Reinstall or update the Mouse driver

The problem may be caused by a corrupted or an outdated mouse driver. To fix it, you have to update or reinstall the mouse driver. How? Follow these steps:

• Open the Devices Manager from the Win X Menu.
• Then locate the Mouse and other pointing devices and right-click on the mouse driver to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, disconnect the mouse and plug it back in to reinstall the mouse driver.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 2 – Try running the Hardware Troubleshooter

The next thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem with these function keys. To use it, refer to these steps:

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 3 – Try to install OEM specific mouse drivers

Aside from updating or reinstalling the mouse drivers, you might also want to try installing OEM-specific mouse drivers. When you install Windows, it will use a generic driver for all its components. The disadvantage of generic drivers for the mouse is that it limits its functionality. In fact, some also configure the middle mouse button to respond to specific action which does not work without the correct drivers. In such cases, you need to visit the website of your computer’s manufacturers to download and install the latest drivers and then open the software and configure it the way it was before. Keep in mind that some OEMs also offer gestures, so you also have to check on that.

Option 4 – Try to modify some entries in the Registry

If a Windows Update is the one that caused the problem, you could correct it by making some modifications in the Registry but before you proceed, make sure that you create a System Restore point first.

• Tap the Win + R keys to open the Run utility.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_CURRENT_USERControl PanelDesktop
• After that, double click on the “WheelScrollLines” entry on the right pane to open its Properties.
• Now change its value data to “3” and exit the Registry Editor and then see if the issue with the middle mouse button is fixed or not.

Oobesttings error is the blue screen of death error caused by some faulty settings inside the Windows registry. The good news is that this is not a hard error to fix and if by any chance you are one of the unfortunate people getting this dreaded annoying error, please do keep reading because we have several things that you can do in order to eliminate this issue from your computer.

Reboot your system

This is the easiest and straightforward solution and can work sometimes since if the system has not been properly rebooted in a while memory could be filled with various processes and it can trigger oobesettings error. A simple restart of the system can solve the issue by decluttering files and emptying memory.

Scan and repair with SFC

If rebooting the system was not helpful and sadly you still receive an error then let's scan and repair system files by using Windows built-in tool SFC. In order to use this, we will have to run the command prompt in elevated administrator mode. Follow instructions closely. First click on the search icon on the taskbar and type in CMD The command prompt will show as a search result, on the right side click on Run as administrator. Once it opens type in following command: sfc /scannow and press ENTER Wait for the process to finish completely and restart your device after.

Repair the system registry

If the SFC scan has not repaired the issue then we will move to the next solution that involves repairing the system registry itself. Please note that you need to follow step-by-step for provided instructions since playing with the system registry can cause some serious issues if not done properly and can even render the system unstable. That being said, let's begin: Press ⊞ WINDOWS + R to open Windows run dialog Type inside regedit and press ENTER Inside registry editor locate the following key: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager/ Memory Management. and click on it to see properties Inside the properties right-click on CommitLimit value and choose delete. Confirm with yes. Close registry editor and reboot your computer.

Reset Windows 11

If even clearing key inside the registry editor has not helped next step would be to reset the system itself. Press ⊞ WINDOWS + I to open Windows settings and click on System on the left. Inside on the right part click on Recovery In recovery click on the button next to Reset this PC that says Reset PC Choose between keep my files and remove everything (a better option is remove everything, but be sure that you have all your files on a separate drive backed up) Choose between Cloud Download or Local reinstall. Click on next to confirm choices and after that on Reset to start the reset process. Follow onscreen instructions until it is fully done.

Resource hogging is a term when one single application or few of them are taking all system resources for themself causing extreme slow down in the computer and nonresponsiveness. It can be a very frustrating and time-consuming experience and it can cost you money if you can not finish work on time due to this effect. I believe that everyone has experienced at least one slowdown in their IT carrier because of resource-hogging applications and most users do not know how to deal with this. We are here to help you with this issue. Just to be aware that this method shown here is not a method to miraculously speed up your PC or anything similar, this is to be able to detect and recover from extreme slowdowns. Hardware components are still very important and if you can upgrade your computer if it is outdated, please do it because new applications will require a more modern system, and not any kind of tips and tricks will save you from outdated hardware.

Identifying resource hogging app

Now when we got that out of the way let's talk about slowdowns, it is no secret that sometimes an application has bugs and memory leaks that can cause this kind of behavior, and sometimes the application simply takes up too much memory for any other application to work normally. The most simple and straightforward way is to bring up a Windows task manager and inspect running applications and services. You can bring task manager by the key combination of CTRL + SHIFT + ESC If the system is in deep memory deficit you will have to wait for the task manager to open and show itself on-screen. Once opened, click on more details if that view is not opened by default. Once the view expands you will see all running applications with how much RAM memory have they taken and how much CPU they are using.

What to do with app?

Now you are presented with a choice on what to do with the problematic application. If you press the end task button on the bottom right, Windows will kill the application and its processes but any unsaved work inside the application will be lost and unrecoverable in most cases. Or you can try to remove smaller applications running to free up more memory and CPU in order for the computer to catch up. Any choice you make is up to you, but be very careful not to kill Windows essential service by mistake, that will cause immediate system instability with high chances of a system crash.

First time when your computer is turned ON and when Windows is booting it will wait 10 seconds before starting your startup applications. This 10 second is used to load all of Windows services so everything is running smoothly. If by any chance you do not want to wait for this startup delay and wish to start applications right away then keep on reading and follow this guide precisely. This guide will require you to play ad tweak with the registry of Windows, it is always recommended to make a registry backup before attempting any tweaks. Also, it is imperative to follow the guide as it is presented step by step. be aware that this guide will eliminate a 10-second delay for all of your starting applications, there is no way currently to remove delay for only one or a few.

1. Press ⊞ WINDOWS + R to open the run dialog
2. In run dialog type Regedit and press ENTER
3. Locate HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize
4. If the key does not exist, make a new one,  Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\, right-click on the explorer and choose new > key. Name it Serialize
5. Right-click on Serialize and choose New > DWORD (32-bit) Value
6. Name the value StartupDelayInMSec
7. Double click on StartupDelayInMSec and locate Value data
8. Set the value to 0
9. Save changes and Exit Registry editor
10. Reboot

If you want to reverse changes and enable delay again, go back to the Registry Editor and delete the StartupDelayInMSec value.

Valve has released a big update to its online store and distribution platform Steam. Among typical bugs fixing and making the user experience a little more fluid, we have received some major updates as well. Please take note that you need to update Steam itself to the latest version in order to get new features.

Storage management Page update

The storage management page has received a complete redesign and UX overhaul and it is now much easier to manage your game libraries and create new ones. The page itself looks and feels a little console more like but thanks to that it offers a much easier and clearer look and feel. Another thing with the Steam store management page is the ability to move installation files from one location to another. Let’s say that you have two or more hard disk drivers in your machine and that you have SSD that you use for running stuff since it is fast and larger and slower one for storage. Now you can easily and quickly move one installation from one to another in order to take advantage of your faster SSD for quicker LOAD game times without making a new installation.

Steam Download page improvements

The download page has also received some love from Valve by enabling us to now see the installation progress. So far on the download page of Steam, you would only get download progress but it has been updated to show installation progress after download as well now making it more straightforward and giving you a general idea of how much more time there is to wait in order to start gaming. Also, you can now drag and drop items in the download bracket to reorder download orders or place them as active downloads to start downloading right away.

Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.

• Method 1

First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.

• Method 2

The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:

• <windows system>Msdbrptr.dll
• <program files>Common Files\Designers\Msderun.dll
• <windows system>Msstdfmt.dll

The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.