The “Error 0x80070006 The handle is invalid” Error can usually be seen with the WAPT application while trying to record or while trying to manually synchronize from an RDS client. There are also some other niche occurrences of this error and in this guide, we have resolved most of them using simple steps that you can follow to fix your issue as well.
Why do you get the Error 0x80070006 issue?
You might be wondering why the issue occurs in the first place and we were too, upon our investigation, we concluded that the following must be the primary reasons behind its occurrence.
- Corrupted HardDrive Sectors.
- Interference from background services.
- Damaged System Drivers/Registry Entries.
After familiarizing yourself with the causes behind the error, you can now move on to implementing the solutions that have been listed as follows.
Fixing Error 0x80070006 The handle is invalid:
Method 1: Startup Some Services
If certain Windows services aren’t started up and running on your computer, you might get the Error 0x80070006 issue, therefore, we suggest that you start them manually using the steps below.
- Press the “Windows + R” keys on your keyboard to start the Run prompt, type in “services.msc” and press “Enter” to launch into the services management window.
- From here, try to sift through the list and look for the “Volume Shadow Copy” and the “Windows Backup” service.
- Right-click on these services one by one and click on the “Start” button to start them up.
- After doing this, go back and verify if Error 0x80070006 The handle is invalid issue is fixed.
Method 2: Try Performing a Clean Boot
Sometimes, in your computer’s background, there can be a bunch of tasks/applications and services running continuously. If that is the case, you can run into conflicts or memory issues that can trigger certain errors with running applications. To fix that, you can try to run a clean boot which limits the number of applications that run in the background. For that:
- From your keyboard, press the “Windows + R” keys and type in “msconfig” in the prompt that opens up.
- After doing this, click on the “Services” tab from the top, make sure that the “Hide all Microsoft Services” option is unchecked, and click on the “Disable All” button.
- Now that you have disabled the services, click on the “Startup” tab, and from there select “Open Task Manager”.
- This will now list the applications that are set to run at startup, make sure to select all the applications one by one and click on the “Disable” button to prevent them from running at startup.
- Restart your computer and it will now boot in a clean boot state.
- Verify if the Error 0x80070006 is fixed and you can navigate back to the msconfig tab and start enabling a couple of services one by one and restarting every time to check which service or application is causing the issue.
- Once the application/service causing the issue is isolated, you can proceed to disable it permanently or reinstall it.
Method 3: Run an SFC Scan
An SFC scan is a great way to check and fix any driver/registry issues that might exist on your computer. To run an SFC Scan:
- Press the “Windows + R” buttons on your keyboard, type in “cmd” and then press the “Shift + CTRL + Enter” keys from the keyboard to start the command prompt with admin rights.
- Now, type in “sfc /scannow” inside the console and press “Enter” to launch a scan.
- After the scan finishes running, check and see if the error is fixed.
Method 4: Check your Hard Disk for Drive Errors
If there are any bad sectors on the Hard Drive that you are using, they can cause memory allocation issues during the runtime of an application. Therefore, we suggest that you go through the following steps to ensure that there aren’t any memory-related issues. For that:
- From your keyboard, press the “Windows + R” keys which will launch the Run prompt.
- Now, type in “cmd” and press the “Shift + CTRL + Enter” key combination to start with admin rights.
- From here, type in the following two commands to run a complete disk check scan.
DISM.exe /Online /Cleanup-image /Scanhealth DISM.exe /Online /Cleanup-image /Restorehealth
Method 5: Uninstall Windows Updates
Some Windows updates have been known to cause issues with WAPT and other applications/clients. Therefore, we suggest that you uninstall some known problematic updates. To do that:
- Press “Windows + R” to start the Run prompt.
- Type in “Control Panel” and press “Enter” to launch into the control panel.
- From here, Click on the “Uninstall a Program” option and select the “View Installed Updates” button which will lead you to a screen that will list the installed updates.
- From the list, right-click on the “KB4480970” update and select the “Uninstall” button which will remove this update from your computer.
- Check if uninstalling the KB4480970 update fixes the Error 0x80070006 with your client.
Method 6: Reconfigure Windows Update Service
If you are getting Error 0x80070006 while trying to install Windows Updates, it might be because the update service might be running its own processes instead of running them in shared mode. If that is the case, we can change them to run in share mode using the method below.
- Press “Windows + R” from your keyboards to start the Run prompt, type in “cmd” and press “Shift + CTRL + Enter” to start with admin rights.
- Now, type in the following command to check the details of the process.
sc query wuauserv
- Check the “Type” of the service and if it says “OWN” anywhere in the text, try to run the following command to change it to share.
sc config wuauserv type= share
- After doing this, check to see if the issue is fixed.
Method 7: Reconfigure Windows Update Service’s Registry Settings
While the above solution works for some users, for others, the issue is related to the service not having certain privileges that allow it to run smoothly. In these steps, we will be adding to the privileges of the Windows Update Service. For that:
- From your keyboards, press the “Windows + R” keys to launch into the Run prompt.
- Type in “Services.msc” and press “Enter”.
- Enter the following address in the registry editor.
- After this, double-click on the “RequiredPrivileges” option, and at the end of the list, add the “SeDebugPrivilege” entry.
- Save your settings and reboot your computer.
- Verify if this fixes the Error 0x80070006 with Windows Update.
Method 8: Create a new GPO (FOR APP-V Related Issues)
Some users were facing the Error code: 0x45500D27 – 0x80070006 or Error code: 0x45500D27 – 0x8007000 while trying to synchronize from RDS Client manually or while trying to perform other operations. If you use GPO to populate the App-V Client settings on the RDS Client, as an alternative you can do this manually without using GPO. However, if you insist on using GPO, try to create a new GPO with similar settings which should fix the issue.
Method 9: Extend the Handle Validity
For users that are getting this error on PowerShell or on certutil while trying to dump the CA Database, this is because the Handle Exception is triggered after no action is triggered within the ViewIdleMinutes period. To circumvent this issue, you can try to increase the Handle Validity which will extend this period.
- Log in to the CA server and ensure that you have administrative permissions.
- On the server, launch into an elevated console session.
- Type in the following command and press “Enter” to execute it which will extend the Idle period.
certutil –setreg CA\ViewAgeMinutes Y
- Replace, “Y” with any number that is most appropriate depending on the data you are trying to process.
Method 10: Change Enterprise Vault Server’s Registry Entries
Some users got this issue with EV Server where the “Error 0x80070006 The handle is invalid” error was triggered along with an Event ID 7292. If this is the case, you can circumvent the issue by changing registry values as we have done below.
- For a 32-bit OS, navigate to the “HKLM/Software/KVS/Enterprise Vault/Indexing” address and for a 64-bit one, navigate to the “HKLM/Software/Wow6432Node/KVS/Enterprise Vault/Indexing” address.
- From there, look for the “MaxIndexServers” option, double-click on it, and change its value to “10”.
- Also, change the value of the “SearchChunkSize” to “3000”.
- After doing this, navigate to the “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management” address, and here, double-click on the “PoolUsageMaximum” entry on the right side.
- Change its value to “50” and save your changes.
- In the end, double-click on the “PagedPoolSize” entry and change its value to “0xFFFFFFFF”. Make sure to select the “Hexa-Decimal” option for this and save your changes before you exit.
- Restart the server for these changes to take effect and check to see if this fixes the Error 0x80070006.
Method 11: Edit your Download Code for SRSS Service (FOR SRSS USERS)
If you are using the SRSS service to download something and are getting the error, you can simply add “Response.Flush()” to the end of your download code which should fix the issue.
Method 12: Modify some Server Settings (FOR IIS USERS)
There are some configuration changes that you can make to ensure that the issue doesn’t occur for you. For that, follow the steps that we have listed below.
- From your IIS, navigate to the “Virtual Directory Properties” option and check if the “Execution Permissions” has been marked as “Scripts and Executables”.
- If that is the case, change it to “Scripts Only” and check to see if that fixes the issue.
- If the issue is still not fixed, on the server running your website, type in and execute the following command in the console.
- Verify if this fixes the issue.
Method 13: Kill Webserver Processes (FOR IIS USERS)
In certain cases, you can create and run a “.bat” file to kill all the currently running web server processes which can sometimes fix the error in question. For that:
- Create a “.bat” file with the following code inside of it.
taskkill /fi "imagename eq webdev.webserver40.exe"
- After saving the changes, run the “.bat” file and check if the issue is fixed.
Sometimes, a simpler restart to your IIS server can fix the issue, also ensure and verify the user login credentials to ensure that is not causing the issue.
The steps above have been useful in fixing the issue for most users, however, if you are still experiencing the issue, feel free to contact us.