Setting Standard Desktop icons on Windows 11

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.

Error Code 49 – What is it?

Error Code 49 is a common device driver error that users encounter on any Windows 2000 and later operating system versions. The error occurs when the connected peripheral devices fail to function properly due to an overload of the system hive’s size. The error when prompted pops up on your screen with the following message:

"Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)”

The error causes unattached devices to be displayed on the system hive list.

Solution

Error Causes

Error Code 49 mainly results from problems in Windows registry system files; the system hive in the Windows registry exceeds its size limit. The system hive is part of the Windows registry and it is where files regarding devices are contained along with user preferences and applications. The devices will not work until the system hive size is brought back to normal levels.

Further Information and Manual Repair

There are several ways you can use to fix your error code. Here are the following.

Method 1 – Uninstall unused devices

One of the best ways to address the error code is to uninstall the unused devices which are listed on your computer’s system hive. To do this:

• Log in using an Administrator account
• Click the Start button and then click ‘Run’
• In the box, enter the command:
• "set devmgr_show_nonpresent_devices=1 cd%SystemRoot%System32 exit" and click enter
• Open Device Manager, click ‘View’, and then choose ‘Show hidden devices’ to see unused devices.
• When you can see the list, click on the device you want to uninstall by selecting the ‘Driver’ tab and then select ‘Uninstall’.
• After uninstall is complete, restart your computer.

Method 2 – Use System Restore

If the error still persists, you can use system restore to eliminate the problem. Here is how you can do so:

1. Log in using an Administrator account
2. Click ‘Start’ button and select All Programs > Accessories > System Tools > System Restore
3. Click ‘Restore my computer to an earlier time’ and click ‘Next’
4. Select the last Windows restore point from the ‘On this list, click a restore point’ list, and click ‘Next’
5. Click ‘Next’ on the confirmation window to proceed
6. Restart your PC after restoration is complete

By restoring the system via a last saved system checkpoint, you can obtain undamaged Windows system files that can help avert the error code.

Method 3 – Manually uninstall and reinstall the device driver

If using system restore does not work in resolving the error code either, you may have to resort to manually uninstalling and then reinstalling the device driver causing the problem. This would be necessary since the remaining incomplete files due to a partial removal or installation of programs is what results in the error code. By uninstall and reinstalling the device driver program, it would lead to the completion of the files. You can do this by firstly logging in as Administrator and open Device Manager. Select the device that is causing the problem and double click it and make sure that the peripheral is connected properly to the PC. Upon opening, click on the ‘Driver’ tab and then select ‘Update Driver’. Make sure to refer to the system documentation that you received with your PC or computer to check for the motherboard details and driver specifics.

Method 4 – Use software to automatically download the driver

Manually uninstalling and reinstalling the driver will do the trick; however, it may be time-consuming, especially when you would have to resort to your hardware user manual. Therefore, using a program such as DriverFIX can save you a lot of time and frustration in having your device work properly on your computer. DriverFIX, with its user-friendly approach to help you fix your PC issues, comes with an integrated database that detects which drivers you need to reconfigure within just a few seconds and downloads it automatically. It further ensures that your drivers are installed in their entirety leaving no room for any incomplete files to remain that create Error Code 49. It also has the added advantage of being able to backup and restore your files should there be the slightest possibility of system file damage. DriverFIX is the answer to fixing your PC error codes accurately and quickly. Click here to download DriverFIX to fix Error Code 49 quickly and effectively!

What is Error 0x00000024?

Error 0x00000024 can be seen when you start up and a screen comes up asking which mode you would startup in. Regardless of the mode you select, it leads up to the Windows screen with the loading bar and your computer crashes from there onwards. When you press F8 in order to select the “Disable Automatic Restart On System Failure” option, that is when this error shows up:

ST0P 0X00000024 (x00190203, 0x82700550, 0xc000012, 0x00000000)

Due to this error, both Safe and Normal modes become inaccessible.

Solution

Error Causes

If you’re having this error then it is the indication of an issue with the file NTFS.sys. Further, there might also be problems with the IRP (Interrupt Request Packet) or the disk may have been corrupted. There are multiple other causes of this error, including heavy fragmentation of your hard drive or problems caused by your antivirus software.

Further Information and Manual Repair

First and foremost, you are suggested to run Chkdsk. In order to do this, you have to enter your BIOS and select CDROM as your primary booting device. Now follow the below-mentioned steps:

1. Insert your Windows XP installation CD into the CDROM and reboot your PC.
2. Press any key to proceed with the boot from CD when you are prompted to do so.
3. When the Windows XP setup menu shows up, hit the “R” key to proceed with repairing Windows.
4. If there is only one Windows installed on your computer then hit the “1” key and proceed by pressing enter. If there are more than two Windows then hit the number which is associated (according to the screen you are viewing) to the Windows you want to repair. Usually, this is C:/Windows and associated with “1” but if that is not the case then you should simply press the number that corresponds with the windows you want to repair and proceed.
5. Now, you will see a screen that prompts you to enter your administrator password. Most people don’t have an admin password and in that case, you should simply hit enter and you’d be good to go. If you do have an administrator password, however, then you should type it in, hit enter, and proceed.
6. When the DOS prompt shows up, type in chkdsk/f and hit return.

If you see no improvement in solving Error 0x00000024, and the problem keeps persisting, then you should start over. But this time you should type sfc/scannow instead of chkdsk/f and hit return. There are a few other complex methods that you can try as well but this is the most recommended procedure as it is easier, quicker, and most likely to fix the error.

I often switch between my desktop speakers and headphones and because of this I very often use the volume adjustment bar to adjust sound levels so it is not too loud and each time when I set it I get annoying BEEP at the end. Now personally this might not bother you and you might want to leave it since it can be a useful feature to tell you how much volume is loud but if you are adjusting multiple times volume during the say it can become really frustrating to hear it each time, especially when switching to headphones and it beeps into your ears. In this guide, I will show you how to remove the beep so it is not heard anymore when you adjust the volume. Please know that beep is part of the Windows sound scheme and you can either remove specific sound with a completely silent wave or just turn off all windows alert sounds.

• Open Windows settings and go to system > sound
• in system sound, go to the right part of the screen and click on the sound control panel
• In the sound control panel click on the Sounds tab
• In the sounds, tab click on the drop-down menu under the sound scheme and choose no sounds.

There you go! You have successfully removed annoying BEEP each time you adjust the volume in Windows 10

If the Sleep option is missing from the Power Menu then this could be caused by the power settings, local group policy configuration, etc. in your computer. Based on the reports of users who experience the same problem, the issue occurred after they’ve updated or upgraded their Windows 10 computers. As you know, the sleep mode is quite useful in certain cases and is utilized by most users. If you put your computer in sleep mode, it actually minimizes the power usage of your computer while at the same time keeps your current session running. So if sleep mode is suddenly missing, then that could be a problem but worry not for this post will give you possible fixes to resolve the issue. Make sure to follow each one of them carefully to achieve good results.

Option 1 – Check the Power settings

As mentioned, one of the reasons why the Sleep option is missing could be the power settings in your computer. To check this possibility, make sure that you’ve enabled the sleep mode in the Power options setting window. How? Refer to these steps:

• First, go to the Start menu, and from there open Control Panel.
• Next, set the View by Large icons and select the Power Options.
• After that, click on the “Choose what the power buttons do” option on the left-hand side.
• Then click on the “Change settings that are currently unavailable” option and make sure that Sleep is checked under the Shutdown settings.
• Afterward, click on Save changes.

Option 2 – Modify the Local Group Policy

If the Power setting isn’t the cause of the problem, then you might want to check the Local Group Policy and modify it. There is a dedicated policy for showing the sleep option in the power menu and if this policy is disabled, then it’s no wonder why you don’t see the sleep option in the power menu. To change this policy, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “gpedit.msc” in the field and hit Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration -> Administrative Templates -> Windows Components -> File Explorer
• Look for the “Show sleep in the power options menu” option from the right-hand side pane and double click on it.
• Now change it to Enabled and click on the Apply and OK buttons to save the changes made and restart your computer.

Option 3 – Try to turn on Standby

Standby, also known as InstantGo, is a feature in Windows 8 and 10 that allows users to maintain network connectivity after a computer has been put into sleep mode. Thus, if this feature is disabled, it can cause the Sleep option to disappear from the power menu. To turn it on, follow these steps:

• Tap the Win + R keys to open Run.
• And type “Regedit” in the field and tap Enter to open the Registry Editor.
• Next, navigate to this path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPower
• From this path, look for the “CsEnabled” key on the right-hand side of the pane and double-click on it.
• Set its value to “1” and click OK to save the changes made.
• Now reboot your PC.

Note: If you were not able to find the CsEnabled key, then this indicates that your computer does not support the Standby feature. And if that’s the case, proceed to the next given option below.

Option 4 – Try to install a Video Card driver

On the other hand, some users reported that the problem was caused by the video card driver. And if your computer lacks the video adapter driver, it can also cause the same problem. Windows 10 typically install the video card driver on its own, however, there are rare cases when it doesn’t which is why you have to do it yourself manually. All you have to do is go to your manufacturer’s website and look for the video card driver, download it and then install it. Once you’ve installed the video card driver, reboot your computer and check if it has fixed the problem.

What is Windows 10X

Windows 10X is a new version of Windows that has been built from the ground up for new PCs and will begin shipping on hardware in 2021. It's built on top of a new modern version of Windows called 'Windows Core OS' that guts legacy components and features in favor of contemporary user experiences and enhanced security. This means everything from the Windows Shell to the underlying OS has been rebuilt with modern technologies.

As a result, Windows 10X does not support legacy Win32 applications at launch. Windows 10X PCs in 2021 will be able to run Microsoft Edge, UWP, and web apps. Legacy Win32 application support will arrive at a later date, however. When it does, Win32 applications will run in a secure container by default, meaning those legacy applications cannot affect system performance and battery life when closed. Windows 10X is a much more secure and stable OS as a result of this, as there's no opportunity for legacy apps to cause bitrot.

Windows 10X features a new shell of the user interface that has been built with modern technologies. It's an adaptive user experience that can adjust depending on the "posture" of your device. For example, with a foldable PC, the user might want to use it in several different ways; as a laptop, or tablet, or in tent mode for movies. Because of this, the user interface must adapt to provide the best experience no matter which way your device is being used. This also means that legacy shell elements, such as the Control Panel, File Explorer, and error dialogs and icons are gone on Windows 10X. As Microsoft has rebuilt the entire shell, it doesn't include any of the legacy things that make Windows 10 so inconsistent when it comes to UI. The Windows Shell on Windows 10X should be much more consistent. At launch, Windows 10X will only be available on traditional clamshell PCs aimed primarily at the education and enterprise markets. The platform will eventually ship on the new devices from factors such as foldable PCs, but that won't be happening in 2021.

Start menu

Microsoft is redesigning the Start menu experience on Windows 10X with a focus on productivity. It features a system-wide search bar along the top that can also search the web and a grid of installed apps below that in place of live tiles. It also has a "recent activities" area that dynamically updates with things the user might want to jump straight into, such as recent Office documents and visited websites. The apps list can be customized, with the ability for users to rearrange which apps show up in the first few rows.

Taskbar

Windows 10X also has a new adaptive Taskbar that features a centered design. The Start and Task View buttons appear in the center, with running and pinned apps appearing between the two. When you open an app, the Start and Task View buttons gently spread apart, giving the Taskbar a much more fluid appearance. There are some new animations; the Start and Task View buttons have their own animations when clicked on, and there's a subtle bounce to app icons when you minimize running apps to the Taskbar. In addition to the new design, there are also up to three different Taskbar sizes: Small, medium, and large. Large is great for tablets, while medium and small mimic the usual sizes we already have today on Windows 10. On tablets, users can now swipe up anywhere on the Taskbar to access the Start menu, making it easier for touch users to access their apps list. You no longer have to hit the specific Start button to access your Start menu.

Action center

In addition to the new Start and Taskbar experiences, there's also a new Action Center to compliment them. This new Action Center puts more emphasis on quick actions, with the ability to jump into specific quick actions for further control without leaving the Action Center at all. It's also designed in such a way that mimics a control center, with notifications housed above it in a separate box. This new Action Center includes things like volume controls, power options, and battery percentage. There's also a new music control UI that appears in the Action Center when music is playing from a supported app.

State separation feature

Unlike Windows 10, Windows 10X features something called "state separation" which is how the OS lays itself out on a drive. Windows 10 today installs everything into a single partition, which means the user can access system files, as can apps and potential attackers. On Windows 10X, everything goes into its own read-only partition. So OS files are locked away, as are app files, as are drivers, and the registry. The only thing the user and applications can access is the user partition. This means that malware or viruses can't get in and affect the system because those programs are only able to operate in a single partition, and that assumes they're able to get outside of the app container system Microsoft has built. All apps on Windows 10X run in a container and need explicit permissions to access things that are outside that container. This is already how UWP apps work on Windows 10, and Microsoft will be extending that to Win32 apps on Windows 10X when support for Win32 apps arrives.

Launch date and info

Windows 10X will launch this spring first for commercial markets. Commercial markets include education and enterprise industries looking for sub-$600 PCs for students in the classroom or first-line workers. Windows 10X won't be launching on consumer PCs in 2021, meaning you won't find it on a flagship Dell or HP device. It's also only for clamshell PCs, with foldable, tablets, and other form factor support coming in 2022 and beyond. Windows 10X will launch without an in-box Mail and Calendar app. It's been removed from the first version of Windows 10X because the platform is aimed at commercial markets that will likely use Outlook Web or stream Outlook via Windows Virtual Desktop. Users can opt to reinstall the Mail and Calendar apps from the Microsoft Store if they wish. Windows 10X for mainstream markets won't happen until 2022 when Win32 app support among other features comes to the OS as part of the Windows 10 "Nickel" release scheduled for the first half of 2022. Because Windows 10X is a new operating system, it will not be released as an update for existing Windows 10 PCs. Users won't be able to install Windows 10X on a device that didn't come with Windows 10X, to begin with. There won't be any official ISO media and you won't be able to buy Windows 10X on its own to install on your existing device. It's for new PCs only. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

If you suddenly encountered an error when you try to run the Windows Sandbox that says, “Windows Sandbox failed to start, Error 0xc030106, The virtual machine or container exited unexpectedly”, read on as this post will guide you on what you can do to resolve the problem. According to security experts, this kind of error in Windows Sandbox is due to some issues with the supporting virtualization component. It could also be caused by other factors and to fix it, there are several potential fixes you need to check out. You can try running the Windows Sandbox as an administrator. You should also make sure that all the supporting processes are running properly, as well as try to install any pending Windows Updates.

Option 1– 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 options below.

Option 2 – Ensure that all the supporting processes and services 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
  • Virtual Disk
  • Hyper – V Virtual Machine
  • Hyper – V Host Compute Service
  • Container Manager Services
• 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 3 – 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.

If you like to travel but you do not have a navigation device and a place where you are traveling does not have internet coverage do not worry, Windows offline maps are here to help. Traveling in today's world often requires that we have some sort of navigation system, wherever that be a dedicated navigation device, maps on your mobile phone, or something similar. Maps on mobile-phone are nice but they drain the battery of the phone fast and being on a road might require that we have access to our phone, just in case of an emergency call, and dedicated navigation devices often cost a lot of money. Lucky for us Windows comes with a maps feature where you can check local maps and orientate with their help and even if you are in an area where you do not have internet coverage you can still use maps via offline mas mode in Windows. This feature will require that you sacrifice little HDD space because you will need to download maps that you will need and some time preparing in order to find and download maps that you will need but in the end, it is worth it, you have a full map system completely offline and independent of the internet. So in order to prepare all maps that you will need, follow this guide step by step and enjoy your trip.

1. Select Settings from the Start menu.
2. Click System.
3. Select Offline maps.
4. Click the + button next to "Download maps".
5. Select the continent where your desired country is located.
6. Select the region you want to download. Depending on the area, you can download a whole country or you'll have to drill down to a smaller region (for example, with Canada and the USA).
7. Repeat for any additional regions you want to have as offline maps. You can download more maps while other maps are currently downloading.
8. Pack your bags
9. GO!

Fatal Error c000021a - What is it?

Fatal Error c000021a is a type of Windows stop error also known as the blue screen of death (BSoD) error. When this error occurs, it causes the computer screen to go blue and locks the user out of the current activity. This error code is fatal and can lead to serious issues like system crashes and freeze. The error code is usually displayed in the following format:

STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000)

Solution

Error Causes

Fatal Error c000021a occurs when the Windows kernel detects that either Winlogon.exe or Csrss.exe service processes have stopped responding or failed to load.  When this happens the error code pops up on the screen. Nonetheless, this is not the only reason for the occurrence of this error. There are plenty more reasons why Fatal Error c000021a may pop on your computer screen. These include:

• Missing or corrupt hardware drivers
• Faulty hardware
• Windows System Restore failed during the rollback process
• Malware or viral infection
• Registry issues

No matter what the reason may be, it is advisable to fix the error right away without any delays. Remember it is a fatal error and can cause a great deal of damage to your PC.

Further Information and Manual Repair

Fatal Error c000021a is a serious PC issue but this does not mean you have to hire an expert to get it fixed. The good news is that this error is actually quite easy to resolve. You don’t have to be a technical whiz or a computer programmer to fix Fatal Error c000021a on your PC. Here are some do it yourself methods to fix this error code right away without any hassle: Let’s get started:

Method 1: Update Your PC Drivers

As we mentioned about corrupt or missing drivers can be one of the many reasons for the occurrence of this error. So, check the drivers first. Perform a driver scan and make sure all your drivers are updated.

Method 2: Perform a Windows System Restore

To do this, first launch Task Manager by pressing CTRL+SHIFT+ESC on your keyboard. Now click on the application tab and then click ‘New Task’ then browse. After that, go to C:\Windows\System32\Restore  folder and then double click the rstrui.exe file. This will help start system restoration. Your computer will reboot during the process and hopefully, the error will be resolved. Nonetheless, if the error still persists then try methods 3 and 4.

Method 3: Scan for Viruses

Sometimes Fatal Error c000021a may also occur due to malware infection. Your PC may be affected by viruses hidden in different locations without you knowing about it. Therefore to resolve this error, it is recommended to run an antivirus and scan for viruses. If detected, remove them right away to fix the error code.

Method 4: Repair the Registry

Another method to resolve Fatal Error c000021a code on your system is to repair the registry. The registry stores all the information and activities performed on the system. If it is not cleaned frequently, it gets loaded with too many files unnecessary and obsolete files like the junk files, cookies, internet history and temporary files which corrupts and damages the registry thereby generating blue screen of death error codes like Fatal Error c000021a. Though you can repair the registry manually it can be both time-consuming and slightly difficult especially if you are not a computer programmer. Therefore it is advisable to download a registry cleaner to fix it right away.

Automatic Repair with Restoro.

Whether the Fatal Error c000021a code occurs due to viral infection or registry issues, download Restoro. This is a next-generation, advanced, and multi-functional PC Fixer. This software is deployed with multiple utilities such as a powerful registry cleaner, an antivirus, a system optimizer, and more. The registry cleaner scans the entire PC and detects all types of registry issues at once. It cleans the registry, wipes out all the unnecessary files, and restores the registry back to normal. Simultaneously, the antivirus embedded in this software detects all types of viruses including malware, adware, spyware and Trojans and removes them in seconds. The system optimizer feature ensures the speed and performance of your PC are not compromised during the repairing process. It ensures your PC works at its optimal speed. Restoro is a one-stop solution for all your PC needs. It has a user-friendly interface making it easy for all levels of users to work around. It is compatible with all Windows versions Click here to download Restoro and resolve the Fatal Error c000021a code on your PC today!

As you know, Microsoft Store is the ultimate source of applications for Windows 10 devices and it’s turning to be the hub for various applications. In fact, aside from applications, it has also become a source for movies, books, TV and even buying hardware directly from Microsoft and many more. Although downloading goes smoothly most of the time, depending on your internet connection, there are also times when you might experience slow download speeds while downloading apps and other things in the Microsoft Store. There are several factors that could be causing this kind of issue. It can be due to the Microsoft Store app itself or it could be enforced speed limiter on the application or it could be due to a corrupted Microsoft Store cache, or it could be due to the Windows Update service running in the background, and so on. To fix this problem, you can try to reset the Microsoft Store cache, or set the bandwidth limit for downloads, or try to re-register the Microsoft Store app via Windows PowerShell. Before you proceed with the troubleshooting options provided below, make sure that your internet connection is stable enough to download apps and games. You also have to check if there is an update or a massive download in progress. Once you have these things covered, follow the given options below.

Option 1 – Try to reset the Microsoft Store cache

Just like browsers, Microsoft Store also caches as you view apps and games so it is most likely that the cache is no longer valid and must be removed. To do so, follow the steps below.

• Right-click on the start button and click on Command Prompt (administrator).
• Next, type in the command, “exe” and tap Enter. Once you do, the command will clear the cache for the Windows Store app.
• Now restart your PC and afterward, try opening Microsoft Store again and then try to install your app or update your computer again.

Option 2 – Try to set the bandwidth limit for downloads

• Tap the Win + I key combination to open the Windows Settings app.
• After that, navigate to Update & security > Windows Update.
• From there, select the Advanced options located on the right-side panel.
• Next, select Delivery Optimization and check the box for “Limit how much bandwidth is used for downloading updates in the background under the Download settings section and then set the slider to 100%.

Option 3 – Try to re-register the Microsoft Store app via Windows PowerShell

• Tap the Win + X key combination or right-click on the Start button and click on the Windows PowerShell (Admin) option.
• If a User Account Control or UAC prompt appears, just click on Yes to proceed and open the Windows PowerShell window.
• Next, type in or copy-paste the following command to re-register the Microsoft Store app and tap Enter:

powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRootWinStoreAppxManifest.xml

• Wait for the process to be completed and then restart your computer.