Fixing SYNTP.SYS Blue Screen error in Windows

What is Error 1723?

Error Code 1723 is a peculiar error type common in Windows PC. It is related to the Windows Installer package. This error is displayed in the following format:

"Error 1723- There is a problem with this Windows Installer package. A DLL required for this install could not be run. Contact your support personnel or package vendor...”

You are most likely to come across the error code 1723 if the Java installation is not completed successfully. In other words, the error indicates that the installation process has failed.

Solution

Error Causes

The 1723 error may occur due to several reasons, the most common being:

• Corrupted installers
• Files are not extracted successfully
• Registry problems
• Missing DLL files

Further Information and Manual Repair

To resolve this issue on your PC, you don’t always have to hire a professional technician and pay hundreds of dollars to get it fixed. The error code 1723 may not be a common Windows PC error but it is easy to fix. Here we have listed some of the best and easiest DIY ways to resolve this error on your system. These solutions are so easy to perform that even if you are not a computer programmer or technically adept, you can work through them and resolve the error in just a few simple clicks. So, let’s get started:

Solution 1: Install the latest Java Version

If the Java version previously installed on your system is not working properly and showing 1723 error messages then it is advisable to install the latest Java version. However, to do this first you will have to uninstall the old version and then download the latest Java version on your PC from a trusted website to ensure it does not contain malicious viruses and malware.

Solution 2: Ensure the Required Files are extracted in the ‘Temp’ Folder for Installers

Another method to resolve the 1723 error code is to check whether the required files are extracted in the temp folder for installers or not. The error may occur if the location is incorrect and the account is not permitted to extract files in the temp folder. In this scenario, the best way to resolve the issue is to change the permissions of the temp folder. This can be done by logging in to your account and opening file explorer or ‘My Computer’. Now copy and paste this link address in the address bar: DL:UsersUSERNAMEAppDataLocal. Please note, here DL is the drive letter of the Windows drive, and in the username insert the username of the account that you are using. Now right-click the ‘temp’ folder. Select properties and click on the Security tab. After that click edit below the list and press add. Again type the username here and click OK. The next step is to select the added account from the list and tick ‘FULL CONTROL’ box under ‘Permissions for Username’. Click OK and then close the properties. Once this process is complete, now try running the installer again. This will most likely resolve the issue. Nonetheless, if the error still persists, then this means the underlying cause of the error is deeper than you think. The error may be related to registry issues. In such situations, try solution 3 to fix the error 1723 on your system.

Solution 3: Download Restoro.

When the error code 1723 is triggered due to registry issues, then it is advisable to scan your PC with Restoro. Registry issues should be resolved immediately because they pose serious threats to your system. It can lead to system failure, crash and valuable data loss. Registry basically saves practically all the information and activities performed on your PC including the unnecessary and obsolete files like junk files, cookies, temporary files, and invalid entries. If these files are not removed they can corrupt the registry, damage dll files and installers thereby generating error codes like 1723 on your system. The easiest way to repair and clean the registry in seconds is to run Restoro on your PC. It is a smart, intuitive, advanced, and multi-functional PC repair tool. It is embedded with multiple powerful utilities and is a one-stop solution for all PC related issues. This software is compatible with all Windows versions. It is deployed with a highly functional registry cleaner that scans and detects all registry issues on your PC and removes them right away. It wipes out the unwanted files, repairs the damaged dll files and restores the registry. Other powerful utilities that are embedded in this software include an antivirus, a system optimizer and Active X controls and class modules. To resolve 1723 error code on your PC today, click here to download Restoro.

Corsair is well known for RAM memory modules for PC but then it has expanded to PC peripherals and even selling some pre-build computers as well in past few years. New Corsair expansion now includes a laptop line, starting with their new gaming laptop Voyager.

Voyager laptop is packed with a mechanical keyboard and MacBook-like touch bar for your typing and pointing needs. It is built with a 16-inch QHD+ screen packing 240Hz that is run by Radeon 6800M GPU. Also inside lurks AMD 16 thread Ryzen 9 6900HS CPU, Wi-Fi 6E support, Dolby Atmos audio, and full HD 1080p WEB camera.

The keyboard has low-profile mechanical Cherry MX switches with per-key RGB lightning and above is what Corsair calls a macro bar, with 10 shortcut buttons and a small LCD in the center.

Corsair is also including a few features that tie in with its other products. Many of the company’s keyboards, mice, and other accessories use the ‘Slipstream’ USB wireless adapter, which is built into the Voyager laptop. The macro bar is also configured using the same software used for the Elgato Stream Deck, a popular product sold by Corsair.

What is ‘Entry Point not found dll’ Error?

Entry Point not found dll errors are common in Windows PC. These errors indicate poor PC maintenance. An entry point is basically the memory address inside the dynamic link library. It contains the call being made. A dynamic link library on the other hand is a collection of small programs which use and request this call to run and load programs successfully on your PC. However, when this process is unable to be executed successfully, you come across ‘entry point not found dll’ error messages.

Solution

Error Causes

Generally speaking, some of the typical causes of ‘entry point not found dll’ errors are:

• Missing, corrupted, and damaged dll files
• Registry overloaded with invalid entries
• Disk fragmentation
• Viral infection

It is advisable to resolve these ‘entry point not found dll’ errors on your PC immediately because dll errors can cause you a great deal of inconvenience as you may be locked out and unable to access your desired programs. Furthermore, if dll errors are left unresolved, such errors can expose your PC to serious threats like system failure, system damage, corruption, and crash.

Further Information and Manual Repair

Though ‘entry point not found dll’ errors are critical errors but the good news is that these can be easily resolved. To fix dll errors on your PC, you don’t always have to hire a professional technician or be a computer programmer yourself. Here are some of the best DIY (do it yourself) ways to resolve ‘entry point not found dll’ errors on your system:

1. Reinstall the Deleted Program

This method to resolve ‘entry point not found dll’ error code is very basic. It is advisable to uninstall and then reinstall the deleted program to retrieve the missing or deleted dll files. Here’s why: dll files are shared files. There are multiple programs on your PC that may be using one type of dll file to load. Now when you uninstall a program that you no more need on your PC, chances are that it may also delete that particular dll file. And when this happens the other programs supported by the deleted dll file are unable to load. Therefore, in such an event the best way to retrieve the missing dll file is to uninstall the program that displays the errors message and then reinstall it. This will help you restore the missing dll file and run the program successfully.

2. Install an Antivirus and a Registry Cleaner

As mentioned above, ‘entry point not found dll’ errors indicate poor PC maintenance. If you don’t maintain your system, the registry overloads with bad and invalid entries, redundant and obsolete files, junk files and cookies. These files acquire a lot of space which damages dll files and the registry. Furthermore, due to data volume overload and less storage space, files are then saved in different places. This is also known as disk fragmentation. When these files are called, it takes a lot of time for the disk to consolidate fragmented data and execute the function successfully. To resolve these issues, you need to clean and restore the registry. Though this can be done manually it may be slightly complicated and time consuming therefore it is advisable to install and run a registry cleaner.

Restoro.

In addition to this, due to poor PC maintenance, viruses and malware can also enter your system unknowingly through file downloads and phishing emails. These can also damage dll files. To remove viruses and malware from your PC it is important to run an anti-virus. Instead of downloading both tools separately on your system, we recommend Restoro. This is a multi-functional and advanced PC fixer embedded with an intuitive algorithm and a user-friendly interface. It includes multiple utilities including a powerful antivirus, a high functional registry cleaner, and Active X controls and class scanner. It also functions as a system optimizer. By running this software on your system, you can easily scan all registry issues and viruses simultaneously. It repairs the damaged registry and dll files, removes unnecessary files and all types of malicious software. It is compatible with all Windows versions. It is easy to use and high on performance. It is a one-stop solution for all ‘entry point not found dll’ errors on your PC. In just a few clicks you can resolve system errors and optimize your PC performance dramatically. Click here to download Restoro and resolve ‘entry point not found dll’ errors.

One of the important functions in the Windows operating system is the Task Scheduler. It can automatically run various tasks at a certain time where you’ll have to add a task that needs to be executed and then choose the time it has to run at. So when that time comes, the Task Scheduler will run the task automatically. However, some users reported getting an Error 0x80070057 where the Task Scheduler fails to start. This kind of error may be due to a disabled service that prevents the service from running. It is also possible that the antivirus program interfered with the task – it could be that the Task Scheduler is somewhat in the block list since the antivirus adds it to the list automatically when it’s installed. On the other hand, it could be that you lack administrator-level privilege which is why the Task Scheduler was not able to carry out the task. To fix this issue, here are some suggestions you can try.

Option 1 – Try to restart the Task Scheduler service

As mentioned, it is possible that the Task Scheduler service could be disabled. You could have disabled it when trying to enhance your computer’s performance and whatnot. Thus, you need to verify if it’s running or not and then restart it.

• First, you need to tap the Win + R keys on your keyboard to open the Run dialog box.
• Next, type “services.msc” in the field and click OK or tap Enter to open the Windows Services Manager.
• You will see a list of Services and from there, look for the Task Scheduler service and double click on it.
• After that, go to the General tab and click on the Startup Type options and then select “Automatically” from the given list.
• Click on the “RUN” option and select the “Restart the Service” option.
• And click on the “After Second Failure” option and then select the “Restart-Service” option again.
• Now click on the “After Subsequent Failures” tab and select the “Restart the Service” option.
• Finally, click on the Apply and OK buttons and then run the Task Scheduler and see if the issue is now fixed.

Option 2 – Try to temporarily disable the anti-virus program

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed in your computer. Thus, disabling them or any security software installed on your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like the Task Scheduler Error 0x80070057 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program for the meantime and check if it fixes the error or not.

Option 3 – Run the Task Scheduler with an administrator account

Like pointed out, the Task Scheduler Error 0x80070057 may be due to the lack of admin privileges. Thus, you have to log in to an administrator account and try running the Task Scheduler again. It is also recommended that the administrator account you’re going to use as a password when logging in.

Option 4 – Repair the Task Scheduler by deleting corrupted tasks

Note that a single corrupted file can cause big problems so this option is quite important. And for you to delete a corrupted task or any task from the Task Scheduler, you have to use the Registry Editor if you are not able to use the Task Scheduler interface. To do so, follow these steps:

• Tap the Win + R keys to open the dialog box for Run.
• Next, type in Regedit and click on OK or tap Enter to open the Registry Editor.
• Then navigate to this path: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTree

Note: In this path, you can see all the tasks that are currently set in the Task Scheduler. And since it would be hard to tell which one of them is corrupted, you have to delete the latest one in Task Scheduler last. But before you do so, make sure that you take note of the ID of the tasks. And for you to get the ID, you have to select the task you wish to delete and double click on the ID string located on your right-hand side, and then copy it in the Notepad.

• Right-click on the task name and then delete it.
• After that, delete the very same GUID which you have copied earlier from these folders:
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheBoot
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheLogon
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheMaintenance
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCachePlain
• ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionScheduleTaskCacheTasks

Note: You might not see the same GUID from these folders but if you see it, delete it right away.

• Next, navigate to this location: C:/Windows/System32/Tasks
• Delete the very same tasks you just deleted from the Registry Editor.
• Restart your PC and check if the Task Scheduler is back to its normal state or not.

Kernel_Data_Inpage_Error - What is it?

Kernel_Data_Inpage_Error is a BSOD (blue screen of death) error. Also, know as a 0x0000007A Stop error. This bug check indicates that the requested page of kernel data from the paging file failed to be read into memory. In simple words, this means that Windows has trouble reading from the memory. This can apply to both kinds of memory: stored memory on your hard drive and also the dynamic memory in your RAM. The Kernel_Data_Inpage_Error turns your computer screen all blue, stops the program being executed, and sometimes even leads to abrupt system shut down.

Error Causes

Kernel_Data_Inpage_Error may occur due to numerous reasons. The exact cause of this error can easily be found by going through the code displayed in the parameter of 0x00000007A. Let’s take a look at Kernel_Data_Inpage_Error parameter codes and the underlying causes of its occurrence:

• 0xC0000009A- This parameter code triggers missing nonpaged pool resources
• 0xC0000009C- This represents the installed hard disk drive has bad sectors.
• 0xC0000000E- This indicates a hardware failure or an incorrect drive configuration

Further Information and Manual Repair

No matter what the cause for Kernel_Data_Inpage_Error may be, it is advisable to fix it immediately as blue screen of death error codes are considered to be critical PC errors that can cause serious damages and even result in valuable data loss. Here are a couple of ways to repair this issue on your system:

1. Call the ‘Chkdsk’ (check disk) command on your system.

Windows XP, Vista, and 7 users can call this command, by pressing Windows Key +F and type in ‘chkdsk’ and run. However, you can’t run it while actively using Windows but you can always schedule it to start automatically the next time your computer turns on. Wrap up what you need and then reboot. Chkdsk disk checking process can take a long time, especially on large and slow hard drives. To run this command on Windows 8, open Windows search by pressing Windows Key+ F and then type ‘cmd’. Then right-click on the command prompt and choose the option ‘Run as Administrator’. To continue with the disk checking process, here you will be prompted to provide your administrator authentication. Once you insert the administrator authentication, type the command ‘Chkdsk C:/f/r/x” where the letter ‘C’ indicates the drive you want to examine and repair. Run it to scan for Kernel_Data_Inpage_Errors on your system. Chkdsk command will detect and repair errors on the hard drive and then automatically reboot.

Limitations to this Solution:

‘Chkdsk’ is a value-adding inbuilt disk checking tool in PC new Window versions; nonetheless, this command has certain limitations. It is time-consuming. You may have to wait for a long time for it to scan your system. Also when disk check is running, you will have to stop all other activities on your system. Furthermore, Chkdsk does not scan and fix all registry errors and other PC-related errors. So, you can’t be 100% sure that it will resolve all the Kernel_Data_Inpage_Errors on your PC.

The Blue Screen of Death error or BSOD is definitely not an issue to face on your computer. Many users, if not all, have already experienced this headache at least once. One of these BSOD errors is the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error. The bug check error code for this is 0x000000FC and is usually caused by outdated or faulty drivers. In some cases, it could also be caused by an error in the Random Access Memory or RAM. This kind of error in the RAM might be physical, based on drivers, or even some kind of unwanted malware. So basically there are lots of possibilities why this particular BSOD error pops up. If you are currently facing this BSOD error, read on and carefully follow the suggestions given below but before you do that, make sure to create a System Restore point just in case something goes wrong. This way, you can always undo those changes using the System Restore point. Once you have that covered, proceed to the options given below to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error.

Option 1 – Try updating Windows 10 with all the security patches and updates

You might be able to fix the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY error by simply updating your Windows 10 computer with all the security patches and updates. To do so, go to Settings then proceed to the Windows Update section > Update & Security > Windows Update, and then click on the Check for Updates option. After you do that, it will automatically find and install all the latest security patches and feature updates from Microsoft.

Option 2 – Try updating all your drivers

From time to time, drivers get corrupted or outdated so it’s no surprise that they conflict with the operating system and cause errors like the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To fix the problem, you need to update all your drivers. Follow the steps below to update your drivers.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver’s name and select “Update Driver Software” or “Uninstall”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC.

Note: You also have the option to go directly to the website of your graphics card manufacturer and check if there’s a new update – if there is, download it.

Option 3 – Try running a Memory Check using Windows Memory Diagnostic

As mentioned, this error might be caused by some issues in the memory. To resolve it, you need to run the Memory Check on your Windows 10 PC. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 4 – Try using the System File Checker via Command Prompt

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the ATTEMPTED EXECUTE OF NOEXECUTE MEMORY BSOD error. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Microsoft’s initial Windows 11 hardware requirements were not really well received by users and they were not really clearly represented from the start making a lot of potential customers slowly drift away from the hype. It seems that Microsoft has acknowledged this since they have changed their tune about system hardware requirements for the upcoming Windows 11. It seems that Windows 11 will be able to be officially installed on unsupported computers but with a little inconvenience.

What is a catch?

Windows 11 will still have the same hardware requirements and if the PC meets them, that computer will be officially supported, other ones (any that can run Windows 10) that do not meet system requirements can still run Windows 11 but the system will have to be clean installed. So no upgrade option for old computer users, just a clean install. This means of course that you will need to download the ISO image and make a bootable USB in order to install it. Also since you will be doing a clean install do a backup of the hard drive since it will need to be formatted. Also, Microsoft has stated that with unofficially supported PC some driver updates might not be delivered leaving you with either older driver versions or relying on your hardware manufacturer on them. This is still not confirmed by Microsoft, just stated as an option. We will see how it goes.

Conclusion

It is very good that Microsoft has reconsidered its system requirements and will not stubbornly push its initiatives over the top requirements allowing even older computers to install new OS. I am sure over time lot of users will upgrade their hardware and drive into officially supported waters, but it is good that they will be able to use new OS on their current hardware.

We couldn’t update system reserved partition” - What is it?

Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.

Solution

Error Cause

“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.

Further Information and Manual Repair

Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.

To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.

First, know if the System Reserved Partition is whether in GPT or MBR partition style:

1. Open the Run window by pressing the Windows key + R. Type msc in the window then press Enter.
2. Right-click on the Disk where SRP is located then select
3. Click over the Volumes
4. On the Partition Style line, you’ll see which partition style your device is using, either Master Boot Record (MBR) or GUID Partition Table (GPT)

Second, determine which method you will need:

Depending on what partition style your device has and whether you’re currently on Windows 7 or Windows 8/8.1, there are various methods you need to do.

Method 1: Windows 7 or 8/8.1 with GPT partition

1. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
2. Type mountvol y: /s at the command prompt then press Enter. This command will add the Y: drive letter where you can access the System Partition.
3. Type taskkill /im explorer.exe /f then hit Enter. Afterward, restart explorer in Admin mode by typing exe and hitting Enter.

NOTE: While in Admin mode, some apps like OneNote will not run.

4. Open File Explorer then type Y:EFIMicrosoftBoot in the address bar. Hit Enter.
5. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For instance, you want to delete the German language: choose de-DE.
6. Optional: You can also delete unused font files for more space. Type Y:EFIMicrosoftBootFonts in the address bar then press enter.
7. Once you permanently deleted the unnecessary files, reboot the device to return to explorer.exe to normal mode and remove the Y: drive letter.

Method 2: Windows 7 with MBR partition

Doing this method will make a permanent, but small increase in the free space of the device’s SRP.

1. Delete language folders

a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.

c. Choose Change Drive Letter and Paths then select Add.

d. Type Y for the drive letter then click OK.

e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

f. Type Y: at the command prompt then press Enter.

g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.

NOTE: Ensure that the space and period after “f” is included in order for the command to work properly      

h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.

NOTE: Ensure that all files are marked as successful and that no files are marked as failed.

i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.

j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the             language folders you want to permanently delete. Language folders are named      with four letters split with a hyphen. For example: de-DE is the German language          while en-US is the U.S. English language.

2. Truncate the NTFS Log:

a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.

b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.

c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.

3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:

a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.

NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.

b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.

4. Restore permissions

a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.

b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.

c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.

Method 3: Windows 8/8.1 with MBR partition

This method makes a larger, but temporary, increase in the SRP free space.

1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.

2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.

3. Select Add then type Y for the drive letter, click

4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.

5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .

NOTE: Ensure that space and period after “f” are included in order for the command to work properly.

6. Type whoami then hit Enter. Record the username that appears. Afterward, type icacls . /grant <username you got from whoami>:F /t then press Enter.

NOTE: Ensure that there’s no space between the username and “:F” or else the command will not work.

7. Once the command is completed, type attrib -s -r –h Y:RecoveryWindowsREwinre.wim then hit Enter.
8. Open File Explorer and check the drive letter of the external drive you’re using (In this case, let’s assume F: is the drive letter of the external drive so when you see F: for the rest of the steps, this means the drive letter of the external drive you’re using).
9. Type mkdir F:RecoveryWindowsRE in the Command Prompt then hit Enter. Afterward, type xcopy Y:RecoveryWindowsREwinre.wim F:RecoveryWindowsREwinre.wim /h
10. Type C:WindowsSystem32Reagentc /SetREImage /Path F:RecoveryWindowsRE /Target C:Windows to map the new path
11. Verify if the copy was successfully done then type del Y:RecoveryWindowsREwinre.wim /F
12. Return to Disk Management window. Click on the Action menu then hit Check if the device’s SRP now has a larger amount of available space. Once there’s enough space, you can proceed with the upgrade.
13. Upon completion of the upgrade, move back the wim file to the Recovery Partition. At this point, you can re-map now the location by:
    1. Open the Command Prompt then type xcopy F:RecoveryWindowsREwinre.wim Y:RecoveryWindowsREwinre.wim /h and press Enter.
    2. Type C:WindowsSystem32Reagentc /SetREImage /Path Y:RecoveryWindowsRE /Target C:Windows to re-map to the original path.
14. Return to the Disk Management window. Right-click on the Recovery Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Remove.

Method: Download a Powerful Automated Tool

Not inclined to go through a long and technical process (as highlighted above)? Download and install a powerful automated tool and get the job done in a jiffy.

If you receive an error message saying, “Windows Update cannot currently check for updates because updates on this computer are controlled”, while trying to change the Windows Update preferences or manually update, then read on as this post will guide you in fixing it. You can mostly encounter this error in managed systems where an Administrator controls the permission on the operating system. The reason why you are not able to modify the Windows Update preferences or manually update your system is that a group policy prevents you from doing so and that the only user who can do these things is none other than the administrator of the system. Troubleshooting this kind of problem is the same as when you troubleshoot an error message that says, “Some settings are managed by your organization”. In such cases, you need to check both the Windows Update Group Policy and Registry settings. If you’re just a standard user, you have to contact your system administrator regarding this issue and if you are the administrator, you can make adjustments to the system settings via the Registry Editor and the Group Policy Editor. Refer to the instructions given below for detailed instructions.

Option 1 – via the Registry Editor

If you are using the Home edition of Windows 10 and you want to change the policy for non-admin users on your local computer, then you can use the Registry Editor for that. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows

• From there, look for the key named “WindowsUpdate” in the Windows folder and if it does not exist, you can just right-click on the Windows folder and select New > Key.
• Now name the new key “WindowsUpdate” and create a new sub-key under the newly created key and input “AU” as its name.
• Keep AU selected and then right-click anywhere in the right pane and select New > DWORD (32-bit) Value.
• Then name the Value as “AUOptions” and right-click on AUOptions and select Modify.
• Next, change the value of the Value data to “5” and click OK to save the changes made to the settings. Note that the Value Data of 5 refers to the policy to allow the local admin to choose the setting.
• Now restart your computer once you’re done and check if non-admin users can now modify the Windows Update settings or update Windows.

Option 2 – via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” and hit Enter to open the Group Policy Editor.
• Next, navigate to this folder: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
• Now look for the “Configure Automatic Updates” policy on the right pane and double click on it to open its Properties.
• After that, shift the Radio button to “Enabled” and from the drop-down menu for Configure automatic updating, select option 5: Allow local admin to choose the setting.
• Then click on Apply and OK to save the changes made to the settings.
• Restart your computer and check if the problem’s fixed or not.

As of late, many users reported getting an error in Windows Sandbox that has an error code of 0x80070015. According to users, they encountered this error when they tried to start Windows Sandbox. Based on the error code, it seems that there are some problems with the supporting services of Windows Sandbox that trigger the error. It is possible that these services are misconfigured or that they are outdated and have to be updated. Here’s the complete message of the error:

“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”

If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.

Option 1 – Make sure that all the supporting processes and services of Windows Sandbox are running properly

If running Windows Sandbox as an administrator didn’t fix the error, you have to ensure that all related processes for Windows Sandbox are running properly. To do that, follow these steps:

• Tap the Win + R keys to launch the Run utility and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
• Next, from the list of services, look for the following services in the given order:
  • Network Virtualization Service: (Startup type: Manual)
  • Virtual Disk: (Startup type: Manual)
  • Hyper – V Virtual Machine: (Startup type: Manual)
  • Hyper – V Host Compute Service: (Startup type: Manual)
  • Container Manager Services: (Startup type: Automatic)
• After you find the aforementioned services, restart each one of them.
• Once done, try to open the Windows Sandbox again and see if the error is fixed or not.

Option 2 – Try to install any pending Windows Updates

If the second option still didn’t work, then you might want to check Windows Updates on your computer and see if there are any pending Windows Updates you have to install. All you have to do is go to the Windows 10 Settings app and then go to the Windows Updates section and click on the “Check for updates” button to check if there are any pending updates that are needed to be installed. This could fix the Windows Sandbox Error 0x80070015.

Option 3 – Try to run Windows Sandbox as an admin

• In the Start Menu, scroll down until you see the entry for the Windows Sandbox.
• Then right-click on it and select More and then select the “Run as administrator” option to open it with admin privileges.
• Next, if a User Account Control or UAC prompt pops up, just click on Yes to proceed.
• You should now be able to open the Windows Sandbox without the error. However, if the error persists, proceed to the next given option below.