Error Invalid Data 0x8007000d
| Error Number: | Error 13 |
| Error Name: | ERROR_INVALID_DATA |
| Error Description: | The data is invalid. |
| Hexadecimal: | 0xD |
| Developer: | Microsoft Corporation |
| Software: | Windows Operating System |
| Applies to: | Windows XP, Vista, 7, 8, 10 |
Compatible with Windows 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall
Plus for quite sometime but recently I ran into a problem, it requested that I reactivate. So I opened up my Toolkit 2.4.3 and clicked 'Activate' but got this error. ERROR CODE: 0x8007000D. ERROR TEXT: The data is invalid. I am running Windows 8.1 x64 bit if that helps. RyanMonster: Beginner. Mine was Windows 10 64-bit Pro, and I was trying to make it 'self-activating'. Tried multiple official builds, including latest svn1108.The flavour of the executable (GCC vs. RPC) didn't make a difference and yielded the same result.
Symptoms of Error 13
- “ERROR_INVALID_DATA” appears and crashes the active program window.
- Your PC frequently crashes with Error 13 when running the same program.
- “The data is invalid.” is displayed.
- Windows runs sluggishly and responds slowly to mouse or keyboard input.
- Your computer periodically “freezes” for a few seconds at a time.
These 13 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Windows Operating System) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your ERROR_INVALID_DATA error occurs is a critical piece of information in troubleshooting the problem.
Causes of Error 13
- Corrupt download or incomplete installation of Windows Operating System software.
- Corrupt Windows registry keys associated with Windows Operating System.
- Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
- Another program maliciously or mistakenly deleted Windows Operating System-related files.
- ERROR_INVALID_DATA.
Windows System Error Codes such as “ERROR_INVALID_DATA” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring.
Windows System Error Codes Knowledgebase
Article ID:
120882
Article Author:
Last Updated:
Popularity:
star rating here
Optional Offer for WinThruster by Solvusoft
EULA Privacy Policy Terms Uninstall
Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall
Below is a list of troubleshooting steps to resolve your ERROR_INVALID_DATA problems. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effort.
Please Note: Click the [ ] image to expand the troubleshooting instructions for each step below. You can also click the [ ] image to hide the instructions as you proceed through each step.
Step 1: Repair Registry Entries Associated with Error 13 |
Manually editing the Windows registry to remove invalid ERROR_INVALID_DATA keys is not recommended unless you are PC service professional. Incorrectly editing your registry can stop your PC from functioning and create irreversible damage to your operating system. In fact, one misplaced comma can prevent your PC from booting entirely! Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster [download] (Developed by Microsoft Gold Certified Partner) to scan and repair any Error 13-related registry problems. Using a registry cleaner [download] automates the process of finding invalid registry entries, missing file references (like the one causing your ERROR_INVALID_DATA error), and broken links within the registry. A backup is automatically created before each scan, with the ability to undo any changes in a single click, protecting you against the possibility of PC damage. The best part is that repairing registry errors [download] can also dramatically improve system speed and performance. Caution: Unless you an advanced PC user, we DO NOT recommend editing the Windows registry manually. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. To manually repair your Windows registry, first you need to create a backup by exporting a portion of the registry related to ERROR_INVALID_DATA (eg. Windows Operating System):
The next steps in manually editing your registry will not be discussed in this article due to the high risk of damaging your system. If you would like to learn more about manual registry editing, please see the links below. We do not claim any responsibility for the results of the actions taken from the content linked below - complete these tasks at your own risk. Windows XP Windows 7 Windows Vista |
Step 2: Conduct a Full Malware Scan of Your PC |
There is a chance that your ERROR_INVALID_DATA error could be related to a malware infection on your PC. These malicious intruders can damage, corrupt, or even delete Windows System Error Codes-related files. Furthermore, there's a possibility that the 13 error you are experiencing is related to a component of the malicious program itself. Tip: If you do not already have a malware protection program installed, we highly recommend using Emsisoft Anti-Malware (download here). They offer a malware removal guarantee that is not offered by other security software. |
Step 3: Clean Out Your System Junk (Temporary Files and Folders) With Disk Cleanup (cleanmgr) |
Over time, your computer accumulates junk files from normal web surfing and computer use. If this junk isn't occasionally cleaned out, it can cause Windows Operating System to respond slowly or provides an ERROR_INVALID_DATA error, possibly due to file conflicts or an overloaded hard drive. Cleaning up these temporary files with Disk Cleanup might not only solve your 13 error, but can also dramatically speed up the performance of your PC. Tip: Although Disk Cleanup is a wonderful built-in tool, it will not completely clean up all of the temporary files on your computer. Other programs that you frequently use such Microsoft Office, Firefox, Chrome, Live Messenger, and hundreds of other programs are not cleaned up with Disk Cleanup (including some Microsoft Corporation programs). Because of the shortcomings of the Windows Disk Cleanup (cleanmgr) tool, we highly recommend using a specialized hard drive cleanup / privacy protection software such as WinSweeper [download] (Developed by Microsoft Gold Partner) to clean up your entire computer. Running WinSweeper [download] once per day (using automatic scanning) will ensure that your computer is always clean, running fast, and free of ERROR_INVALID_DATA errors related to temporary files. How to run Disk Cleanup (cleanmgr) (Windows XP, Vista, 7, 8, and 10):
|
Step 4: Update Your PC Device Drivers |
ERROR_INVALID_DATA errors can be related to corrupt or outdated device drivers. Drivers can work one day, and suddenly stop working the next day, for a variety of reasons. The good news is that you can often update the device driver to fix the Error 13 problem. Finding the exact driver for your Error 13-related hardware device can be extremely difficult, even directly on the Microsoft Corporation or related manufacturer's website. Even if you are experienced at finding, downloading, and manually updating drivers, the process can still be very time consuming and extremely irritating. Installing the wrong driver, or simply an incompatible version of the right driver, can make your problems even worse. Because of the time and complexity involved in updating drivers, we highly recommend using a driver update tool such as DriverDoc (Developed by Microsoft Gold Partner) to automate the process. DriverDoc updates all of your PC device drivers, not just those associated with your ERROR_INVALID_DATA error. DriverDoc's proprietary One-Click Update™ technology not only ensures that you have correct driver versions for your hardware, but it also creates a backup of your current drivers before making any changes. Maintaining a driver backup provides you with the security of knowing that you can rollback any driver to a previous version if necessary. With updated device drivers, you can finally unlock new hardware features and improve the speed and performance of your PC. Please Note: Your ERROR_INVALID_DATA may not be related to hardware driver problems, but it's always a good idea to ensure all of your PC device drivers are up-to-date to maximize PC performance. |
Step 5: Utilize Windows System Restore to 'Undo' Recent System Changes |
Windows System Restore allows you to 'go back in time' with your PC to help fix your Error 13 problems. System Restore can return your PC's system files and programs back to a time when everything was working fine. This can potentially help you avoid hours of troubleshooting headaches associated with ERROR_INVALID_DATA errors. Please Note: Using System Restore will not affect your documents, pictures, or other data. To use System Restore (Windows XP, Vista, 7, 8, and 10):
|
Step 6: Uninstall and Reinstall the Windows Operating System Program Associated with ERROR_INVALID_DATA |
If your ERROR_INVALID_DATA error is related to a specific program, reinstalling Windows Operating System-related software could be the answer. Instructions for Windows 7 and Windows Vista:
Instructions for Windows XP:
Instructions for Windows 8:
After you have successfully uninstalled your ERROR_INVALID_DATA-associated program (eg. Windows Operating System), reinstall the program according to the Microsoft Corporation instructions. Tip: If you are positive that your 13 error is related to a specific Microsoft Corporation program, uninstalling and reinstalling your ERROR_INVALID_DATA-related program will likely be the solution to your problem. |
Step 7: Run Windows System File Checker ('sfc /scannow') |
System File Checker is a handy tool included with Windows that allows you scan for and restore corruptions in Windows system files (including those related to ERROR_INVALID_DATA). To run System File Checker (Windows XP, Vista, 7, 8, and 10):
|
Step 8: Install All Available Windows Updates |
Microsoft is constantly updating and improving Windows system files that could be associated with ERROR_INVALID_DATA. Sometimes resolving your Windows System Error Codes problems may be as simple as updating Windows with the latest Service Pack or other patch that Microsoft releases on an ongoing basis. To check for Windows Updates (Windows XP, Vista, 7, 8, and 10):
|
Step 9: Perform a Clean Installation of Windows |
Caution: We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve Error 13 problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately (download a highly-recommended backup solution) to protect yourself from permanent data loss. This step is your final option in trying to resolve your ERROR_INVALID_DATA issue. Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system. Furthermore, a clean install of Windows will also quickly clean out any and all 'junk' that has accumulated over the normal usage of your computer. Please Note: If 13 errors still persist after a clean install of Windows, your Windows System Error Codes problem MUST be hardware related. If that is the case, then it is likely you will need to replace the associated hardware causing the 13 error. |
Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall
Operating System Information
ERROR_INVALID_DATA error messages can occur in any of the following Microsoft Windows operating systems:
- Windows 10
- Windows 8
- Windows 7
- Windows Vista
- Windows XP
- Windows ME
- Windows 2000
Are You Still Experiencing Error 13 (ERROR_INVALID_DATA) Issues?
Please reach out to us anytime on social media for more help:
Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall
Recommendation:Scan your PC for computer errors.
Optional Offer for WinThruster by Solvusoft EULA Privacy Policy Terms Uninstall
About The Author:Jay Geater is the President and CEO of Solvusoft Corporation, a global software company focused on providing innovative utility software. He is a lifelong computer geek and loves everything related to computers, software, and new technology.
Browse Errors in Alphabetical Order:
This is driving the whole team crazy. There must be some simple mis-configured part of IIS or our Web Server, but every time we try to run out ASP.NET Web Application on IIS 7.5 we get the following error...
Here's the error in full:
The machine is running Windows Server 2008 R2. We're developing our Web Application using Visual Studio 2008.
According to Microsoft the code 8007000d means there's a syntax error in our web.config -- except the project builds and runs fine locally. Looking at the web.config in XML Notepad doesn't bring up any syntax errors, either. I'm assuming it must be some sort of poor configuration on my part...?
Does anyone know where I might find further information about the error? Nothing is showing in EventViewer, either :(
Not sure what else would be helpful to mention...
Assistance is greatly appreciated. Thanks!
UPDATES! - POSTED WEB.CONFIG BELOW
Ok, since I posted the original question above, I've tracked down the precise lines in the web.config that were causing the error.
Here are the lines (they appear between <System.webServer> tags)...
Note: If I delete the lines between the <httpHandlers> I STILL get the error. I literally have to delete <httpHandlers> (and the lines inbetween) to stop getting the above error.
Once I've done this I get a new 500.19 error, however. Thankfully, this time IIS actually tells me which bit of the web.config is causing a problem...
Looking at these lines it's clear the problem has migrated further within the same <system.webServer> tag to the <handlers> tag.
The new error is also more explicit and specifically complains that it doesn't recognize the attribute 'validate' (as seen on the third line above). Removing this attribute then makes it complain that the same line doesn't have the required 'name' attribute. Adding this attribute then brings up ASP.NET error...
Could not load file or assembly 'System.web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=f2cb5667dc123a56' or one of its dependencies. The system cannot find the file specified.
Obviously I think these new errors have just arisen from me deleting the <httpHandlers> tags in the first place -- they're obviously needed by the application -- so the question remains: Why would these tags kick up an error in IIS in the first place???
Do I need to install something to IIS to make it work with them?
Thanks again for any help.
WEB.CONFIG
Error 0x80070643 Windows 10
Here's the troublesome bits of our web.Config... I hope this helps someone find our problem!
19 Answers
I had these exact symptoms and my issue was similar to Peter's. Was setting up an existing project on a new server. My project referenced the IIS7 URL Rewriting module, but that hadn't been installed yet on the new server. Installing it fixed my issue.
You can use the Microsoft Web Platform Installer to install it. Execute it, select Products, in the left menu select Server and find URL Rewrite in the list and install it.
Or you can download it here.
Dawid Ferenczy RogožanAfter battling with this for a day on a new machine I came across the following links. I was missing the rewrite modules. This fixed everything.
Aha! I beat this problem! My god, it was a beast for someone like me with limited IIS experience. I really thought I was going to be spending all weekend fixing it.
Here's the solution for anyone else who ever comes this evil problem.
First thing to be aware of: If you're hoping this is your solution, make sure that you have the same Error Code (0x8007000d) and Config Source (-1: 0:). If not, this isn't your solution.
Next thing to be aware of: AJAX is not properly installed in your web.config!
Fix that by following this guide:
http://www.asp.net/AJAX/documentation/live/ConfiguringASPNETAJAX.aspx
Then, install the AJAX 1.0 extensions on your production server, from this link:
http://www.asp.net/ajax/downloads/archive/
Update: Microsoft seems to have removed the above page :(
That's it!
Chuck Le ButtChuck Le ButtHad the same problem as above, same error code etc. Setting up a local website on Windows 8. After much searching it was found that we were missing URL rewrite. After downloading it everything was fine. :)
Same issue on Server 2016, IIS 10, 500.19 error. I installed the redirect module and it worked. I do not know why this was not included by default.
To be clear it looks like the web.config from IIS 7 will work, or is designed to work, but the lack of this module gives the really odd and unhelpful error. Googling takes you to a Microsoft page which insists that your site is corrupted or your web.config is corrupted. Neither seems to be the case.
That unhelpful page is here: https://support.microsoft.com/en-us/kb/942055
Windows 10 Backup Error 0x80070002
RobRobI just add an answear because I spent hours trying to solve the same symptoms (but different issue):
A possible cause is a x86 dll in a 64 bits app pool, the solution is to enable 32 bits apps in the application pool settings.
Guillaume86Guillaume86For me, re-registering asp.net for iis did the trick. Hopefully that helps someone else.
ctcctcTo sum up based on answers here and elsewhere:
- Check the .NET version of the app pool (e.g. 2.0 vs 4.0)
- Check that all IIS referenced modules are installed. In this case it was the AJAX extensions (probably not the case these days), but URL Rewrite is a common one.
Another way of getting 500.19 errot for no apparent reason is - missing directories and/or broken permissions on them.
In case of this question, I believe the question asks about full IIS version. I assume this because of this line:
IIS installer usually creates the wwwroot for you and that's the default root folder for all websites and mount point for virtual directories. It always exists, so no problem, you usually don't care much about that.
Since web.config files are hierarchical, you can put there a master web.config file and have some root settings there, and all sites will inherit it. IIS checks if that file exists and tries to load it.
However, first fun part:
This directory will exists if you have IIS properly installed. If it does not exist, you will get 500-class error. However, if you play with file/directory permissions, especially 'advanced' ones, you can actually accidentally deny IIS service account from scanning/reading the contents of this directory. If IIS is unable to check if that wwwrootweb.config exists, or if it exists and IIS is not able to open&read it - bam - 500-class error.
However, for full IIS it is very unlikely. Developers/Admins working with full IIS are usually reluctant regarding playing with wwwroot so it usually stays properly configured.
However, on IIS Express..
Usually, IIS Express 'just works'. Often, developers using IIS Express often are not aware how much internally it resembles the real IIS.
You can easily stumble upon the fact that IIS Express has its own applicationHost.config file and VS creates and manages it for you (correctly, to some extent) and that sort of an eye-opener telling you that it's not that simple and point-and-click as it seems at first.
Aside from that config file, VisualStudio also creates an empty directory structure under your Documents folder. If I remember correctly, IIS Express considers these folders to be the root directories of your website(s) upon which virtual directories with your code are mounted.
Later, just like IIS, when IIS Express starts up, it expects these folders to exist and checks for root web.config files there. The site web.config files. Almost always, these web.config files are missing - and that's OK because you don't want them - you have your **application web.config', they are placed with rest of the content in a virtual directories.
Now, the second fun part is: IIS Express expects that empty directories. They can be empty, but they need to exist. If they don't exist - you will get a 500-class error telling you that 'web.config' file at that path cannot be accessed.
The first time I bumped into this problem was when I was clearing my hard drive. I found that 'documentswebsites' folder, full of trash, I recognized several year-old projects I no longer work on, all empty, not a single file, so I deleted it all. A week later - bam - I cannot run/debug any of the sites I was working at the moment. Error was 500.19, cannot read config file.
So, if you use IIS Express and see 500-class error telling about reading configuration, carefully check the error message and read all paths mentioned. If you see anything like:
Go there exactly where the error indicates, ensure that these folders exist, ensure that IIS worker account can traverse and read them, and if you notice that anything's wrong, maybe it will be that.
BTW. In VisualStudio, on ProjectProperties/Web there's a button 'Create Virtual Directory'. It essentially does this very thing, so you may try it first, but IIRC it can also somethimes clear/overwrite/swap configuration sections in applicationHost.config file, so be careful with that button if you have any custom setups there.
quetzalcoatlquetzalcoatlIn my case, there was something wrong with the .NET Core Windows Hosting Bundle installation.
I had that installed and had restarted IIS using ('net stop was /y' and 'net start w3svc') after installation, but I would get that 500.19 error with Error Code 0x8007000d and Config Source -1: 0:.
I managed to resolve the issue by repairing the .NET Core Windows Hosting Bundle installation and restarting IIS using the commands I mentioned above.
Hope this helps someone!
This may or not be related....I started off with the same error mentioned above, started googling, making changes, getting new errors, endless loop.
The change that got me by that error was messing with the Feature Delegation in IIS Manager under the Management section of the server. I'm sorry I can't remember which one I changed, but googling might help.
That got me past the 1st error into a whole new stream of others, some totally nonsensical. (I would get one error when running under a virtual directory, converting it to an application yielded another error, etec etc). What finally solved this series of errors was:IIS manager, Application Pools, DefaultAppPool, Enable 32-Bit applications=True
I had started this app on a 32 bit windows xp box, and I am now running it on a 64Bit Windows 7 box.
So hopefully this helps someone else.
tbonetboneMy IIS 7.5 does not understand tag in web.configIn VS 2010 it is underline that tag also. Check your config file accurate to find all underlined tags.I put it in the comment and error goes away.
Comment the following lines in the web.config file.
This will work.
stealthyninjaI had the same error. I had an IIS site with .net framework version 2.0, but my app needed 4.0. I changed the version and it worked.
Posting just as a reminder if someone might have the same issue.
NenotlepNenotlepThis lovely detailed error is still present in 2019!I just want to add that if your web.config is valid and accessible it most likely is a dependency issue.
As mentioned by the OP it was a AJAX module, and as by others commonly the Rewrite module.Just keep your eyes open in your web.config what modules and libraries your tags are referencing to since the error code 0x8007000d can be about ANY dependency.
In my case I didn't realize the AspNetCore bundle was missing and had to be installed! So happy I found this post!!
I had the same issue in Windows 7.
The solution was to go to basic settings > connect as > specific user - and log in as a user, instead of the default 'pass-through'
This fixed the issue for me.
Windows 7
Try this,
run cmd as Admin.
Unistall all iis.
Reinstall iis and normaly it's work
Alain
I got this error by putting the <customErrors> tag inside of <system.webServer> instead of <system.web> where it belongs. There was a little squiggle under the <customErrors> tag but I didn't notice it right away.
Make sure all of your IIS features are properly enabled.
- Open Windows Features (Turn Windows features on or off).
Scroll down to Internet Information Services
Open the World Wide Web plus box drop down
- Open the Application Development Features plus box drop down
- Manually check all of the subsequent check boxes, then click ok
protected by Community♦Sep 19 '14 at 11:26
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
