An Easy Guide to Resolving Code 18

This post will guide you in fixing the error 0x80070103 when installing Windows Update. According to users who encountered this problem, Windows Update (WU) fails to install several different updates. This kind of Windows Update error is can mostly be seen in the Windows Update screen inside the update reports although it is also known to occur when a user attempts to install a peripheral driver – only if the Windows Update offers to update the driver through a prompt and when you click Yes. There are several possible causes for this error, it could be that Windows Update is trying to install a particular driver for the second time already which happens when it gets confused by an additional piece of identical hardware like the graphics adapter. Aside from that, the Windows Update might have already installed the driver which is known to occur with unsuitable versions of the already installed driver. In addition, the error could also be due to a third-party program interference like a security program or a utility program that is using the same driver and conflicts with the Windows Update. Here are some suggestions that might help in fixing the Windows Update error 0x80070103.

Option 1 – Install the updates in a Clean Boot State

You might want to try putting your computer in a Clean Boot state and then install Windows Updates again without any trouble. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After that, try to install the Windows Updates or upgrade again.

Option 2 – Try installing the failing driver without using Windows Update

If installing the updates in a clean boot state didn’t help, you can try a manual approach to yield much better results using the Device Manager or by downloading the driver from the manufacturer’s website manually.

• Tap the Win + R keys to launch Run.
• Type in 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. Look for the device driver you and then select either “Update driver” or “Uninstall device”. 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.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.

Note: You also have the option to go directly to the website of your device driver manufacturer and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

Option 3 – Try to run the Windows Update Troubleshooter

You might also want to run the built-in Windows Update Troubleshooter in Windows that could help you in resolving the Windows Update error 0x80070103. All you have to do is go to Settings > Update& security > Troubleshoot > Windows Update. From there, click on the Run the troubleshooter button and follow the next one-screen instructions that appear. After that, restart your computer and check if the error is now fixed or not by trying to install the update once again.

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!

Error code 10, device manager code occurs when Bluetooth or Wi-Fi cannot be enabled. Inside device manager beside device would be yellow exclamation sign and if you go into device properties status would be: This device cannot start. Following are proven solutions that will resolve the issue and provide you with a working device.

Reboot PC, check for switch

This simple solution can usually work in most cases, first thing is to check if by any chance hardware switch for Wi-Fi or Bluetooth is OFF (laptops have a small switch that can turn the device On or OFF), then if you do not have a switch or you made sure it is ON, reboot your system.

Run Network Adapter Troubleshooter

If previous simple step solutions have not proven to be effective run Network Adapter Troubleshooter

1. Press WINDOWS + I to open settings
2. Go to System > Troubleshoot > Other troubleshooters
3. Inside Find Network Adapter
4. Click on Run to start the troubleshooters

Disable and then re-enable Adapter

If the previous solution has not fixed the issue try disabling the adapter and then re-enabling it back.

Update network adapter

Go to the intel website and download the latest driver package. After the download is finished install the latest driver.

Turn ON the WLAN AutoConfig service

1. Press Windows key + R to invoke the Run dialog.
2. In the Run dialog box, type services.MSC and hit Enter to open Services.
3. In the Services window, scroll and locate the WLAN AutoConfig service.
4. Double-click on the entry to edit its properties.
5. In the properties window, click the drop-down on the Startup type and select Automatic.
6. Next, make sure the Service status is started and running.
7. Click Apply > OK to save changes.
8. Exit Services console.
9. Restart PC.

What is 0x3D55? As you know, Windows 10 is loaded with various Universal Windows Platform or UWP apps such as the Microsoft News, Weather, Calculator, Windows Mail, and many other applications that are based on the modern UWP platform of Microsoft that was introduced in Windows 10. Each one of these apps has a shared piece of code in the kernel for them to be able to get executed across any device that runs the Windows 10 OS which includes laptops, PCs, 2-in-1 devices, mobile phones, mixed reality headsets, and many more. However, there are times when the runtime information for these apps ends up getting corrupted which causes them not to function as expected and throws errors like the error 0x3D55. This kind of error can be pinned down when the UWP app malfunctions and you can also find an error message in the Event Log that reads, “0x3D55: Package family <App name with ID> runtime information is corrupted”. So if you encounter this error, read on for this post will walk you through fixing it. There are three suggestions you need to check out to fix this error – first, you can try to reset the Microsoft Store cache, second, you can try to re-register or reinstall the problematic app and lastly, run the Windows Store App troubleshooter.

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, “wsreset.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 – Run the Microsoft Store Apps troubleshooter

The Microsoft Store Apps Troubleshooter will help you in fixing the error 0x3D55. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

1. Tap Win + I keys again to open the Windows Settings panel.
2. Go to Update & Security and then go to Troubleshoot.
3. On your right-hand side, scroll down to find the Windows Store Apps and then click on the Run the troubleshooter option and see if it fixes the problem.

Option 3 – Try to re-register the UWP app via PowerShell

• First, type “command prompt” in the Start Search and right-click on Command Prompt and then select the “Run as administrator” option.
• Next, navigate to this location in the command line utility: C:/Users/<Insert Username>/AppData/Local/Packages
• After that, execute the “DIR” command to view the list of all the directories in the given location.
• Once the list appears, look for the ID of the problematic app and take note of it.
• Now 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 -Command "& {$manifest = (Get-AppxPackage Microsoft.<YOUR APP ID HERE>).InstallLocation + 'AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

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

When you receive Error 0x800704C8 when trying to move a file inside Windows 10 operation is stopped and it can not continue leaving you with the file in its original location without a copy. Several issues can be the cause of this type of behavior and error and after some digging and analyzing we are bringing you various solutions for this error and how to fix it.

Ownership issues

It turns out that not having ownership of fie can cause this error and prevent you from copying it. For some reason, Windows can assume that file is owned or used by another application or process and thus prevents you from making a copy since you do not have ownership of it. Resolving this particular issue will require you to install a third-party application that is tailored for this kind of task. After some talk and research, we found out that there is a freeware application that can solve this issue quite fastly. Unlocker is the name and the download link is here. Once downloaded, install it and run it. Once inside the application browse to the location where you need to change the ownership, click on it to select it, and click OK. Use the No Action drop drown menu to select Move, then click OK

Antivirus Issue

As with other file and application issues, this error could also be a product of antivirus marking it inaccessible to Windows and thus preventing copy or move operation on it. note: Do not turn off Windows defender since it was proven that it is not the cause of this kind of error, so if you are using only Windows defender you can skip this solution. How temporary turning off each security suite is different and it depends on the application itself we can not cover in detail the procedure here. Go to your security suite manufacturer's website and get information there or if you want, go directly to applications and features inside Windows and uninstall the software.

Visual Studio issue

• If the file you are trying to move is part of a Visual Studio project then the issue can be linked directly to Visual Studio itself, luckily the solution is quite easy. All you have to do it to exit Visual Studio and then run it with administrator privileges.
• In order to run Visual Studio with elevated privileges locate its executable file and right-click on it.
• Choose properties and go to the compatibility tab
• Inside compatibility tab check box that says run this program as an administrator

Corrupted system files

If the previous solutions have not provided you with results then you have system file corruption that needs to be fixed. Move from one solution to another as presented below:

1. Run SFC scan

   SFC scan is a built-in Windows tool for solving corrupted system file issues, it is fully automated and does not require from the user any kind of knowledge or information. To run it and scan the system do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) In command prompt type SFC /SCANNOW and press ENTER Wait for the process to finish, do not interrupt it and once it is done, restart your computer

2. Run DISM scan

   DISM scan is similar to SFC scan but it tackles different types of system file corruption and it is recommended to run it also after SFC has been completed. Please note that for DISM scan to be successful you will need a stable internet connection since DISM will replace corrupted files with new ones downloaded from Microsoft. To run it do the following: Press ⊞ WINDOWS + X to open the secret menu Left-click on the command prompt (admin) inside command prompt type: exe /online /cleanup-image /scanhealth followed by ENTER, then type: Dism.exe /online /cleanup-image /restorehealth also followed with ENTER. Leave scan to finish and reboot your PC

Error Code 0x8007232B (Code 0x8007232B) – What is it?

Error code 0x8007232B (Code 0x8007232B) is an error that occurs when you attempt to activate Windows Server 2008 or Windows Vista.

Common symptoms include:

• Attempting to activate Windows 7, Windows 8, or Windows Server 2012 and you receive an error message.
• The error message says: “Windows could not be activated. Key management services host could not be located in domain name system, please have your system administrator verify that a KMS is published correctly in DNS”
• The error message says “The directory name, file name, or volume label syntax is incorrect”.

Error Causes

• Error Code 0x8007232B occurs when you attempt to use media that is volume licensed to install: Windows 8, Windows 7, Windows Vista Enterprise, Windows Vista Business, Windows Server 2012, Windows Server 2008, Windows Server 2008 R2.
• This error code also occurs when the activation wizard is unable to connect to a Key Management Service host computer.

Further Information and Manual Repair

Error code 0x8007232B can be seen when you are trying to activate windows, on several different operating systems. This problem can usually be easily corrected, but in the event that it can't, please contact a computer repair technician. When you try to install any of the previously mentioned Windows products, they use a generic product key to install the volume-based license software. If you do have a KMS host computer configuration and see these error codes, that means the correct DNS entries are not being seen on the computer. If there is not a KMS host computer setup, you need to do this setup, otherwise switch to a MAK product key method, and activate the volume license installation that way.

Method One:

Using a Multiple Activation Key as opposed to KMS activation

1. Click the Start icon, click on All Programs, click on Accessories, right-click on Command prompt.
2. Click on “Run as administrator”. Type in the password or provide confirmation if prompted for administrator password or confirmation.
3. When asked for the command prompt, enter in the following and then hit the Enter buuton: slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx  Note: this placeholder represents the MAK product key.

Method Two:

Configure a KMS host server for the clients to activate against.

A KMS host server needs to be configured for the clients to activate against. When there are no KMS host servers configured near you, install and activate a KMS server key. After this, configure a computer on the network to host this KMS software and publish the Domain Name System (DNS) settings.

Method Three:

When the client cannot locate a KMS host on the network for activation:

1. Verify that your computer has the KMS host installed and activated by using a KMS key that is registered in DNS. You will follow these steps to do that:

1. Click the Start button, click on All Programs, click Accessories, and then right-click on Command Prompt.
2. Click on Run as Administrator. Type the password or provide confirmation if you are asked for an administrator password or for confirmation.
3. In the command prompt box, type the following command and press ENTER: nslookup -type=all _vlmcs.tcp>kms.txt
4. Then open the KMS.txt file generated by this command. The file will contain at least one entry that relays the SRV service location.

2.  A KMS host server registers a DNS SRV record once every 24 hours by default. You should check the registry to see if the KMS host server is registering with the DNS. Follow these steps to do so:

1. Click on Start, type in regedit, and then press Enter.
2. Locate HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsNTCurrentVersionSL and then click on it.
3. The KMS server does not register in DNS if the DisableDnsPublishing subkey is existing and has a value of 1. If this subkey is missing altogether, create a DWORD value called the DisableDnsPublishing. If the dynamic registration is suitable, the subkey value should be changed to 0. Right-click DisableDnsPublishing, click on Modify, enter 0 into the Value data box, and click OK.

Things have stirred lately with Chinas ban on crypto mining and many used GPUs will flow the market probably. But should you buy a used GPU? Short answer: NO, long answer: keep on reading to find out why.

GPU shortage and its cause

As you all know by now, we live sadly in a world struck by a global Pandemic. Due to this awful disease and measures taken against it, many people are either working from home or are at home making the manufacturing of new chips problematic while demand on the market has raised. Throw into that mix crypto mining which has raised in popularity and you have, well today's market where we have GPU shortage. Now with the latest news that China has banned the mining of cryptocurrency, there is to be expected that at some point in time mining cards used there will fit the market in the whole world. Sadly even with a large quantity of GPUs that will become available, the overall price of cards will not be much lowered I am afraid since demand is still very high and many people would not want to purchase used mining cards and neither should you.

Be prepared for the worst scenario

Although this sounds very pessimistic and in most cases, it will not turn out to be true, you should always prepare yourself mentally that you might be in that lower percentage that will end up with a really bad GPU. What has come up to be absolutely true when considering GPU that were mining is that if anything at all can be done to GPU in order to increase performance, it has been done. Miners want to optimize and almost every GPU if could be overclocked, it was overclocked. Extensive mining also means that thermal paste has been dried and it is pretty useless at this point and there is a very high chance that fans and heat sinks will need much cleaning or even replacement raising the price of the card itself for mentioned paste, fans, and heat sinks. There's no way to tell what the previous owner might have done with a graphics card when you're shopping online, so our advice is to assume the worst. Don't trust the seller to give truthful information. Any listing that says it was "never used for mining" at this point is probably a lie.

Age of the GPU matters

Date when GPU itself has manufactured really matters. Newer cards even if used extensively have been used for a much shorter period of time and are not so damaged were ones produced a few years ago have seen a lot of action. Let’s say that you get RTX 3060, In the worst-case scenario it has been mining since late February of 2021 and basically, it is still under warranty so it should behave OK and put some good work in gaming even in that state. On another hand, if we take for example GTX 1080Ti which is 4 years old GPU things start to change drastically. 4 years GPU could be worn out even if it was used just for extensive gaming sessions let alone for mining.

No return policy and seller rating

Most of the time you will run into a product that cannot be returned or no refunds policy. This should bring a red flag right away and deter you from purchase. Sellers with the highest ratings are more trustworthy since many of them will not want to destroy their reputation but these will probably not even have these kinds of merchandise in their store. Buying with a poor rating seller and no return policy on a product is just asking for trouble. And although some stores do have arbitration and will stand on the customer side there is no guarantee for that and it will take too much time to process.

If you really must buy a second-hand GPU

Of course in these troubled times sometimes due to malfunction or any other reason, there would not be another choice than to buy a second-hand GPU. In this case, if there is no other option consider sellers with many positive ratings. If you can buy locally that would even be better or the best-case scenario would be if you could visually see and inspect GPU itself in order to see in what state it is. Look for warranty stickers to see if they are thorn and the card has been tampered with. Also take a good look at screws, if they have scratches card has been opened, probably to replace fan or heating sinks which means that it has worked a lot.

Conclusion

It is very difficult to give the best possible advice on this situation since of GPU shortage, but I would much prefer a new GPU with lower performance than a hi-performance one which was mining.

If you suddenly encounter Error 0x80000003 while trying to execute a random file then read on as this post will show you how you can fix such an error. Obviously, it mostly happens on executable files or .exe files and is most likely caused by the conflict in the execution of some registry files or it could also be caused by missing drivers or it could also be due to some incompatible hardware which is why you’re unable to run the executable file. When you encounter this error, you will see the following error message on your screen:

“The exception Breakpoint, A breakpoint has been reached, (0x80000003) occurred in the application.”

As you can tell, the Windows Executive STATUS message is a warning and if you are given an option, you must select one of the options from the message box. So if you are running the application in an end-user environment rather than in a development environment, you must contact the supplier of the running application regarding this error message since this shouldn’t be happening when a finished program is running. Before you get started executing the troubleshooting guide given below, make sure that you create a System Restore Point first since you will be dealing with some critical settings in Windows. Having done this, proceed to the options provided below.

Option 1 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve Error 0x80000003. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

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

Option 2 – Try to run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the Error 0x80000003. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• 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.

• Restart your computer after the scan is completed.

Option 3 – Perform a Clean Boot

There are some instances that some conflicting programs installed in your computer might be the one that’s causing the Error 0x80000003 to appear. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• From there, start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 4 – Run the Memory Diagnostic Tool to check for Memory leaks

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Option 5 – Try contacting the developer

If you find that you’re getting Error 0x80000003 on only one particular application, then you can try to contact the developer of the software that’s throwing up this error. All you have to do is search the web for the official support channel of the software and discuss the error from there.

As you know, the Microsoft store is a built-in tool in Windows 10 where you can find a variety of applications. It helps users in downloading or updating apps in the system. However, there are instances when you could encounter issues while using it. One of the issues that you could face when using the Microsoft Store app is when it keeps on offering apps you have just updated or when you are not able to update any apps at all. This kind of issue in the Microsoft Store app might be caused by other issues like a damaged Windows Store cache. There are several options you can check out to resolve the problem. You can try to check the registry setting or run the Windows Store apps troubleshooter or clear the Windows Store cache manually or reset its settings. You could also try to re-register the Microsoft Store app. For more details, refer to each one of the options provided below but before you troubleshoot the problem, make sure that you create a System Restore point.

Option 1 – Run the Windows Store App troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the problem in Microsoft Store. This is a great built-in tool from Microsoft that helps users fix any app issues. To use the Windows Store Apps Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Window Store Apps.
• Then click on the Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 2 – Try checking the settings in the Windows Registry

The next thing you can do to fix the problem is to check the Registry settings for the Windows Store.

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionCurrentVersion
• From there, look for the DWORD named “CurrentVersion” and make sure that its value data is set to 6.3, but if it’s not then change its value data to 6.3
• Exit the Registry Editor and restart your computer and then see if it fixed the problem with the Microsoft Store app.

Option 3 – 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 4 – 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.

The file is too large for the destination file system is the error when you try to copy a file larger than 4GB on a drive formatted in the FAT32 file system. FAT32 is the old file system used in previous Windows versions and it was replaced by superior NTFS, altho FAT32 is still used because of its compatibility fact that it could be accessed in various operating systems its disadvantage among others is that it can not hold files larger than 4GB in size. This refers to the size of a single file, so if you have a file that is this large and when you try to copy or move it on a drive formatted in FAT32 you will get this message, and the operation will not be able to complete.

Format drive

In order to actually transfer the file in its glorious size, I am afraid that you will need to format destination drive in NTFS or if you have data on drive which you do not want to lose with formatting, use third-party software to convert file system from FAT32 to NTFS without losing data. I would recommend AOMEI partition assistant, it is a free and proven application letting you both manage your partitions and convert any one of them into another file system without data loss. You can get AOMEI here.

Split file

Another option if you are not keen on installing third-party tools or formating is to divide large files into smaller ones that are less than 4GB in size. You can use any archiving application since built-in Windows ZIP support will not let you split file into various different sizes. The best tool in my humble opinion is WinRAR, but you can choose any proven one. When file is split into parts less than 4GB in size, you will have no issues copying or move the file to the destination drive.