Fix Microsoft Store error 0x80072F30

If you were trying to open File Explorer but it suddenly stopped working and you encounter an error message that states, “An attempt was made to reference a token that does not exist”, read on as this post will guide you in fixing this problem. This problem was initially reported after the April Update and Microsoft was able to fix it right after correcting the build. However, this effort seems futile for some users as recently, some reported getting the same error when they try to open not just Windows File Explorer but also with utilities like Microsoft Management Console or MMC, Visual Studio, Task Manager, Printer, Recycle Bin, etc. Two of the most likely causes of this error are a troublesome Windows Update and corrupted system files. Whatever the cause is, here are some suggestions you can follow to fix the “An attempt was made to reference a token that does not exist” error.

Option 1 – Try to re-register the problematic DLL file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix the ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) control in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 2 – Replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 3 – Perform a System File Checker scan

The System File Checker or SFC scan could detect and automatically repair damaged system files that could be causing the “An attempt was made to reference a token that does not exist” error to pop up. 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. 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 and hit Enter.

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.

Option 4 – Try reverting back to the previous build of Windows

This kind of error might have something to do with a Feature Update so you can try to revert your computer to a previous build of Windows 10 as it could help you fix the problem. In this case, it would better if you refrain from updating your Windows 10 computer until this problem is completely resolved by Microsoft.

nslookup is a command-line tool that helps in finding the DNS records of a website. It sends a name server query to the DNS and obtains the corresponding IP address. Aside from that, it can also perform some complex functionality such as finding details about FTP server, Mail server and many more but most of them are used by administrators. The best thing about nslookup is that it queries the DNS server directly and it does not rely on the cache. On the other hand, there is another tool called PING that is used to verify connectivity. PING sends a packet of information to the IP address or Domain and gets back a response in the form of packets. So if everything goes well, all packets are received but if not, it will help you find out where the delay in the network exactly is. However, the ping command does not always attempt a DNS lookup which means that it might be using the DNS cache and use the IP address available in that table. Although both nslookup and PING help you in identifying the host or IP address, however, they don’t always work and sometimes fail. So if your nslookup works but ping fails on your Windows 10 PC when querying the IP address of a website then it could be caused by many reasons. It could be that the nslookup queries work for you but when you try to use PING, it fails. For instance, if you open the abc.com website, here’s how it will look like:

nslookup xyz.com Server: dns.company.com Address: 192.168.1.38 C:> ping xyz.com Ping request could not find host xyz.com. Please check the name and try again.

The domain is converted into an IP address and then data is sent to that IP address when you use PING. So when a reply comes back it means that the data is going back and forth to that domain without any problem. However, if the DNS fails to resolve the IP address of the website or if your PC does not attempt a DNS lookup, you will receive a similar error message that says, “Could not find host” and so on. To resolve this issue, here are some options that might help.

Option 1 – Reset Winsock, TCP/IP & Flush DNS

Resetting Winsock, TCP/IP, and flushing DNS might help you resolve the issue with nslookup and PING. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 2 – Force Windows to do a DNS lookup using FQDN

• Go to Settings > Network & Internet > Status > Change adapter options.
• From there, right-click on the network and select Properties.
• Next, in case you’re using IPv6, from the list of connections available in the list, select Internet Protocol Version 4.
• Then click on Properties and click Advanced.
• After that, switch to the DNS tab and select “Append these DNS suffixes (in order)” and click on the Add button and then add “.” as a suffix so that each time you query using PING and another tool, it will add a “.” at the end and will force the lookup.

Option 3 – Make sure that there is only one default gateway

If your computer has more than one NIC connected and there are multiple default gateways, then it will most likely create confusion which is why you need to remove the default gateway from the configuration of all NICs and make sure that there is only one default gateway.

Option 4 – Use the Google Public DNS

You might want to change your DNS to Google Public DNS as it could also help you in fixing the nslookup and PING issues. To do so, follow the steps below.

• The first thing you have to do is right-click on the network icon in the Taskbar and select Network and Sharing Center.
• Next, click on the “Change Adapter Settings” option.
• After that, search for the network connection that you are using to connect to the internet. Note that the option might be “Wireless Connection” or “Local Area Connection”.
• Right-click on your network connection and click on Properties.
• Then select the new window to choose the “Internet Protocol 4 (TCP/IPv4)” option.
• After that, click on the Properties button and click the checkbox in the new window for the option “Use the following DNS server addresses”.
• Type in “8.8.8.8” and “8.8.4.4” and click OK and exit.

Option 5 – Check the Windows Host file

You can also try to cross-check the Windows Hosts file to find out if the website you are trying to open has been blocked, because if it is, then it’s no wonder why PING fails even when nslookup works. There are instances when some third-party application modifies the file and adds some websites to the blocklists. So if the website is indeed blocked, you need to remove it from the list.

Option 6 – Delete the WLAN Profiles

Deleting the WLAN Profiles might be a good idea if you are not able to connect to the internet on your computer and if you’re using Wi-Fi. It could be that the networks that were connected previously have gone rogue which is why it is not connecting properly. And so deleting the WLAN profiles might help you in fixing the issue with nslookup and PING.

Option 7 – Reinstall the Network Adapter Drivers

• Tap the Win + R keys to launch the Run window and then type in the “msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and select “Uninstall device”.
• Restart your PC.

A couple of Windows 10 users recently reported getting an error that says, “The group or resource is not in the correct state to perform the requested operation” while opening UWP Applications as well as accessing the File Explorer. You can encounter this kind of error mostly on File Explorer, Microsoft Store application, and other UWP applications. This indicates that this error occurs during both the Windows Classic Application and the Universal Windows Platform Applications. There are several ways to fix this error. You can try to run a System File Checker scan, or run the DISM tool or the Program Compatibility troubleshooter or Windows Store Apps troubleshooter or try to reset or reinstall Windows 10 or the affected application that's not working. However, before you do any of these troubleshooting tips, you can try to perform System Restore first as it could undo the changes you’ve made in the system which might have caused the error.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

If System Restore wasn’t able to fix the error, then you can refer to each one of the following options.

Option 1 – Try to use the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the “The group or resource is not in the correct state to perform the requested operation”. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the DCOM error is now fixed.

Option 2 – Run the System File Checker Scan

Aside from the DISM tool, you can also run a System File Checker scan. It is another built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re getting the 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.

• Reboot your computer.

Option 3 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job. In addition, you can try to run the Windows Store apps troubleshooter as it can also help you resolve the problem.

Option 4 – Reset your computer

• Tap the Win key or click on the Start button located in the Taskbar.
• Then click on the Power button at the bottom right portion of the screen.
• Next, press and hold the Shift key on your keyboard and then click on Restart. This will restart your Pc into the Advanced Startup options.

Note: Once you have access to the Advanced Startup options, you have to go to the setting which allows you to Reset your Windows 10 PC. All you have to do is select Troubleshoot > Reset this PC to reach the following screen

• Afterward, select either the “Keep my files” option and then proceed to the next on-screen instructions that follow to reset your Windows 10 computer without losing your files.

Recently, several users reported an issue on their Windows 10 computers where the taskbar is not visible when they tried to connect to a computer via Remote Desktop Protocol or RDP. The Remote Desktop Connection feature uses the RDP which allows users to access a computer remotely. This is actually different from the taskbar being hidden automatically until the pointer hovers on it since, in this scenario, the taskbar is completely not accessible which makes using the remote computer entirely difficult, if not impossible. There are several suggestions you can check out to resolve this problem, you can try to restart the process of Windows Explorer via Task Manager or you could clear the cache for multiple processes. You could also try to reinstall the Shell Experience components or show the local taskbar in the Remote desktop. Moreover, you could also try to update, uninstall or roll back the display driver/graphics card driver. For more details, refer to each one of the options given below.

Option 1 – Try to restart the Windows Explorer process

The first option you have to try to fix the problem with the taskbar is to simply restart the Windows Explorer process in the Task Manager.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Next, go to the Processes tab and find the process of Windows Explorer.
• Once you find it, right-click on it and select Restart to restart its process.
• After that, restart your computer and see if you can now see the Taskbar.

Option 2 – Try clearing the cache of multiple processes

The next thing you can do to resolve the problem is to clear the cache of many processes in your computer. To do so, follow these steps:

• Open the Notepad app and paste the following content in the text area:

@echo off taskkill /f /im explorer.exe taskkill /f /im shellexperiencehost.exe timeout /t 3 /NOBREAK > nul del %localappdata%PackagesMicrosoft.Windows.ShellExperienceHost_cw5n1h2txyewyTempState* /q timeout /t 2 /NOBREAK > nul start explorer @echo on

• After that, tap the Ctrl + S keys to save the changes you’ve made in Notepad and select the “All files” as its file type, and then name it “CacheClearTWC.bat”.
• Next, go to the location where you saved the file using File Explorer and then run it. This will run a couple of batch scripts which will clear the cache of multiple processes in the system.
• Tap the Win + X keys and select the “Windows PowerShell (Admin)” option to open PowerShell as admin.
• Next, execute this command in the command line: Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “appxmetadataappxbundlemanifest.xml”)}
• After the command has been executed, this will reinstall the Shell Experience components and should fix the problem with the taskbar.

Option 4 – Update, uninstall or rollback the Graphics card drivers

• First, boot your computer into Safe Mode.
• After that, 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. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: You also have the option to go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it.

What is Backup Error 0x80070002?

Error 0x80070002 shows once you’re done backing up files through the Windows Backup program on a system running Windows 7, you see a notification that pops up with a message that reads something like: “Check your backup results. The backup completed but some files were skipped.” You try finding out the reason and you hover over to the Options button beside the message, then you get to read the following lines: “Check your backup results. The backup completed but some files were skipped. View skipped files.” Upon clicking the “View Skipped Files” option, the backup error 0x80070002 pops up on your screen and you’re left scratching your head, wondering what you’re going to do now.

Solution

Error Causes

There are multiple error logs that you will encounter in backup error 0x80070002 as per different conditions. The two most common cases in which this error shows up are stated below:

Case 1

You will see the following message when you press “View skipped files”: “Backup encountered a problem while backing up file C: Windows/System32/config/systemprofile. Error: (The system cannot find the file specified. (0x80070002))” You will face this case if you have backed up a library that included custom folders that were located in your user profile.

Case 2

Upon pressing “View Skipped files” you will encounter the below-mentioned messages: “Backup encountered a problem while backing up file C:/Users<User>AppDataLocalLow. Error: (The system cannot find the file specified. (0x80070002))” “Backup encountered a problem while backing up file C:/Users<User>Contacts. Error: (The system cannot find the file specified. (0x80070002))” “Backup encountered a problem while backing up file C:/Users<User>Searches. Error:(The system cannot find the file specified. (0x80070002))” You are likely to encounter any of these messages in case:

• The Windows Backup program is trying to back up your files in either one or all of these folders (LocalLow, Searches, Contacts).
• All three of these folders don’t exist in your system.

Keep in mind that all three of these folders exist due to the installation of certain programs and applications on your system.

Notes

The backup error 0x80070002 is also found to occur while using USB devices instead of storage devices. Other occurrences include the times when input/output (I/O) operations are performed on the USB device, which results in failure.

Further Information and Manual Repair

To make sure this issue is resolved, you will have to follow either one of the following solutions as appropriate to your situation:

Solution for Case 1

1. Ignore the error. The store files of the custom library in your user profile will not be created as backups.
2. Transfer the library folder from where it currently exists to a place outside its current folder (user profile). For instance, you can move the library folder to an entirely new destination such as “C: My Folders”
3. Remove the library folder from the list of files that you are backing up using the Windows Backup program. Then, add the original place of the library’s content in the list.
4. Go back and check step two. If carried out successfully then add a link to the folder you moved from the library. Check to see if the backup includes the library folder. To make sure, you have to do as follows:

• Go to Start and select your username.
• Hover across to the folder you wish to move, right-click on it and select “Cut”.
• Head to the navigation pane and search for the area you will store the folder in, right-click and select “Paste” so that the folder is moved to that location.
• Right-click on the folder that you just moved and select “Copy”.
• Go back to Start, select your username, right-click any vacant space in your folder and select “Paste Shortcut”.

Note: If you want to store the folder in a different place other than the folder in which it currently exists (user profile), you will need to create a new folder. In order to do so, go to the Windows Explorer menu and look up the root of the drive. Hit “New Folder” and then choose edit to change its name. You can set it as any name for instance, “My Folders”.

Solution for Case 2

You can ignore this error safely. However, if you wish not to see this error in the future during your backup operations then you will need to carry out the following steps:

1. Create all the folders listed in the error message including LocalLow, Contacts, and Searches.
2. Remove all of these folders from the Backup settings to make sure they aren’t being backed up then add the folders which are in their original place. To carry out this procedure, you will have to follow the below-mentioned steps:

• Head over to the Control Panel and open “Backup & Restore”.
• Go to the Backup section and select “Change Settings”.
• Click Next in the Setup backup dialog box.
• Select “Let me choose” in the dialog box termed “What do you want to back up” then proceed by clicking Next.
• Expand Data Files, expand <user> Libraries, expand Additional Locations then proceed by clearing out the AppData Folder, searches, and Contacts checkboxes.
• Expand Computer as well as the item for your system drive (expand Local Disk (D:)), expand users, expand <user>, then go to AppData, Searches and Contacts and mark them if they are present.
• Proceed by clicking next and select “Save Settings” then exit.
• Back to Backup & Restore, select Back up now and your new backup will begin proceeding. The entire process will be complete without any errors now.

If you encounter an error saying, “Invalid file handle” when you try to rename, copy, delete a file or other operations in your Windows 10 computer, then read on as this post will guide you in what you can do to fix it. This kind of error pops up when the operating system tries to carry out an operation on a folder or file using the following words:

CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

When you rename or create a folder or file using the reserved words given above, you could encounter an error that says, “The specified device name is invalid”. This occurs since these words are Windows system reserved words that you can’t use, unlike any other words. Thus, if you have a folder or file which contains any of the reserved words on another computer that runs a non-Windows operating system and you try to copy or rename it Windows, then it’s no wonder why you’re getting this error message. In such cases, you can always click on the Skip button to stop the operation. However, if there are various folders or files, you can just use the Command Prompt to carry out the task. All it takes is a simple command that will get rid of the folder as well as the files in it. How? Refer to the instructions given below. Step 1: Tap the Win + R keys to open the Run utility. Step 2: Next, type “cmd” in the field and then tap Enter to open Command Prompt. Step 3: After opening Command Prompt, execute the following command:

rd \.file-folder-path /S /Q

Note: The “rd” command will remove the directory or the folder while the “\.” command will select the current computer. The “/S” command, on the other hand, helps you in removing all the sub-directories and the files that are in the CON folder. The “/Q” command is not really mandatory since it helps you remove everything silently without any confirmation message. For example, if you have a folder named “CON” located on your Desktop, the path will be like this “C:/Users/<username>/Desktop/CON”. In this case, the command should be like this:

rd \.C:Users<username>DesktopCON /S /Q

However, if the error pops up for a whole different reason, you could use the following command instead to remove the reparse point extended functionality. Once you’ve entered the given command below, you should now be able to delete the file.

FSUTIL reparsepoint delete C:Users<username>DesktopFileName DEL C:Users<username>DesktopFileName

Error Code 17 - What is it?

Code 17 is a typical Spotify error code. Spotify is a music streaming service. Through this software, PC users can browse songs and search by artist, album, and playlist. Simply put, it is an audio player available for BlackBerry, iOS, and Microsoft Windows desktop. You may experience error code 17 if the process fails when downloading Spotify from the internet. The error message is displayed in any one of the following formats:

Error 17: Spotify has encountered a problem and needs to close. We are sorry for the inconvenience. Spotify could not be started (Error code 17)

Some of the symptoms of this error code are program crash, slow Windows performance, and periodic system freeze.

Solution

Error Causes

Error 17 may be triggered by several reasons such as:

• Viral infection
• Incomplete installation of Spotify software
• Corrupt download
• Registry corruption
• Windows Installer service terminated

To use the audio player Spotify successfully on your PC, it is advisable to fix error 17 right away on your system. Delay may cause inconvenience and limit your access to your desired program.

Further Information and Manual Repair

To repair this error code on your PC, you don’t have to hire a professional or be a technical whiz yourself. The good news is that this error is quite easy to fix. You don’t need to be technically sound to resolve it. Here are some proven methods for you to fix error code 17 on your system. So let’s get started:

Method 1 - Make sure that the Windows Installer is running

Sometimes Spotify error 17 may occur if the Windows Installer service is terminated. Therefore before you download, make sure the Windows Installer is running. This is a good way to ensure the error code 17 messages don’t pop up on your PC again. For this here’s what you need to do, first quit all programs. Now go to the start menu and in the search box type RUN, and press enter. In the Open Box, type msiexec /unregister and then press OK to confirm. After that, perform the same steps again, and now in the Open Box type msiexec /regserver and press OK to save. Reboot your PC and try downloading Spotify again. If the program successfully downloads on your system, then this means error 17 is resolved. However, if the error code still persists, then try other methods given below.

Method 2 - Use System Restore to Undo Recent Changes

Another reason for the cause of error 17 is the improper or incomplete installation of Spotify. Improper installations can configure settings and also leave bad entries in the registries. To resolve, use System Restore utility built-in Windows. By using this system tool, you can undo recent changes and resume your computer to its previous condition as it was before the proper installation was attempted. To do this, go to the start menu, then in the search box type System Restore and press enter. Go to System Restore and choose a restore point. Once you’ve selected the point, reboot your PC to activate changes.

Method 3 - Remove Viruses

Viruses can enter and damage your PC if you download software programs from unknown websites. These not only damage your PC but also hinder your ability to install desired programs successfully in this case audio player Spotify. In such an event, simply use an antivirus to remove all viruses infecting your system. After they are removed, make sure you download and install Spotify software from a trusted website.

Method 4 - Repair the Registry

Another cause of error 17 is registry corruption. This occurs due to bad entries, invalid and junk files saved in the registry. To fix the corrupt registry simply download Restoro. This is a user-friendly PC Fixer embedded with a powerful registry cleaner. This software is compatible with all Windows versions. The registry cleaner detects all registry issues, removes all file corrupting the registry, and cleans it immediately in just a few clicks. Click here to download Restoro on your PC and resolve Error 17.

If you are trying to copy or move files to and from your external storage device but you suddenly encounter the error 0x800703EE, then you’ve come to the right place as this post will guide you on how you can fix this error in your Windows 10 computer. This kind of error when copying files may be accompanied by an error message that says, “The volume for a file has been externally altered so that the opened file is no longer valid”. This error prevents you from copying or moving the files to and from the external storage device. This kind of issue might be caused by a service that belongs to a backup program that could be blocking the operation or a conflict with your third-party antivirus program. In addition, the error could also be due to corrupted or outdated USB drivers or it could be caused by a disabled Windows Backup and Volume Shadow copy service. It is also possible that some system files are corrupted or that the drivers for the external device are also corrupted. Whatever the cause is, here are some options you need to check out to fix the error. Before you troubleshoot the error, you might want to try moving the files to another location on your local drive and remove the USB drive and insert it back again. After that, try to move or copy the file to the USB drive and see if it still throws an error. If it does, then you need to troubleshoot the problem further by following each one of the suggestions given below.

Option 1 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 2 – Try checking the Volume Shadow Copy and Windows Backup services

The next thing you can do to fix error 0x800703EE is to check the Volume Shadow Copy and Windows Backup service.

• First, tap the Win + R keys to open the Run dialog box and type “services.msc” in the field, and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Copy service and right-click on it, and then select Properties.
• After that, make sure that its Startup type is set to Manual and that its status is “Started” so if it isn’t, you need to click on the Start button and then on the Apply and OK buttons to save the changes made.
• Once done, look for the Windows Backup Service and repeat the same process you did with the Volume Shadow Copy service.
• After you complete the steps, restart your computer and see if the error is now fixed.

Option 3 – Restart your computer in a Clean Boot State

If a third party program like antivirus is the one that’s causing the problem, you can try to put your computer in a Clean Boot State to isolate the issue by following these steps:

• 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.)
• Now try to copy the files to your external storage device again and check if the error is now gone.

Option 4 – Try to run System File Checker or SFC scan

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

Option 5 – Try to delete the Filter drivers

Note that this option is only applicable if you see the error 0x800703EE accompanied with the “The volume for a file has been externally altered so that the opened file is no longer valid” error message. Before you start, create a System Restore Point first.

• Open the Registry Editor and navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E965-E325-11CE-BFC1-08002BE10318}
• After that, select the “{4D36E965-E325-11CE-BFC1-08002BE10318}” key and check if you can find the “Upperfilters” and “Lowerfilters” value in the right pane. If you can find them, right-click on them and select Delete.
• Once done, exit the Registry Editor and restart your computer.

A slow PC startup can be pretty annoying. This usually results from various computer issues. If your computer is acting sluggishly, here are four ways to speed up your PC startup.

When you get an igfxem.exe error in Windows, it is not really clear what does this means, usually, Windows throw us some code or we get a DLL error, rarely we get an EXE error. So what does this error means? Intel Graphics Executable Main Module, shortly called as IgfxEM module is a part of the Windows operating system. When you run Microsoft .NET Framework applications that use the AS/400 Data Queue ActiveX control (Mseigdq.dll) to read from and to write to IBM iSeries (AS/400) data queues, you may experience this error. In order to overcome this error and cope with it try the following things:

1. Increase Virtual Memory

   Go to the Start Menu and click on Settings. Type performance. Choose Adjust the appearance and performance of Windows. In the new window, go to the Advanced tab and under the Virtual memory section, click on Change. At the bottom of the new window, check what the Recommended value is and how it compares to Currently allocated. If the current setting is significantly less than the recommended, uncheck the Automatically manage paging file size for all drives box at the top of the same windows and then click on Custom size. Enter the Recommended value in the Initial Size box, and a larger figure in the Maximum size box. Click OK to save the new settings.

2. Download and update .NET framework

   Go to the Microsoft website and download the latest .NET framework. Once the download is complete, install the package following onscreen instructions.

3. Reinstall INTEL graphic drivers

   Go to the intel website and download the latest graphic drivers for your graphic card model. Once the download is complete, install the package following onscreen instructions.

4. Run SCF scan

   If all else fails, run command prompt and inside type sfc /scannow