Asked by:
Windows Defender - Error 0x80070057

Question
-
Ok, I keep running into this error when trying to update Windows Defender. Using a fresh install of Vista Ultimate build 6001 with SP1 slipstreamed (DVD image downloaded from Technet). Also, Windows Update is also not working. When you click on check for updates it flashes for a second and then says there are no new updates available. In the windowsupdateclient event log there are windows update errors with the same 0x80070057 error that defender has. Also, next to the errors in the log are entries which say windows update has sucessfully found 4294967295 updates.
Obviously this is not right. I have tried reinstalling from scratch four times now, and each time I have tried restarting the update service & renaming or wiping out the update folders. I'm starting to wonder if there's something wrong with the posted ISO on the technet site, after searching the net the only time I've seen these error's the install was done from one of these images. Anybody have any ideas?Wednesday, June 11, 2008 7:46 PM
All replies
-
Hi CSapanski
Thanks for reposting.
The Windows Defender/Windows Update problems are probably the same issue, since Defender uses WU to get updates.
It's doubtful that the ISO on Technet is corrupt, we haven't seen any others indications of this. It could have been a hiccup when you downloaded or when the ISO image was created? If we cannot fix the problem, you might want to try to download and burn that image again.
The base description for the 0x80070057 error is ERROR_INVALID_PARAMETER.
Here are some procedures you can try.
First, go to the following thread and go through the procedure that I posted there, step by step. This procedure will completely reset all of the WU components and we have had good luck with this resolving a large variety of WU errors.
Windows update error 8E5E0442 - TechNet Forums:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3448011&SiteID=17Be sure to reboot the system after this is finished.
*Note: This procedure will remove the Windows Update History, but will not effect any installed updates.
Let us know the results.
If this post helps to resolve your issue, click the Mark as Answer button at the top right of this message.
This will help others who are having this issue find the answer quicker.
Ronnie Vernon
Microsoft MVP
Windows Desktop ExperienceWednesday, June 11, 2008 8:46 PMModerator -
Hi,
I'm experiencing the exact same problem as CSapanski. Let me quote which are true for me:
1. I keep running into this error when trying to update Windows Defender.
2. Using a fresh install of Vista Ultimate build 6001 with SP1 slipstreamed (DVD image downloaded from MSDN this time).
3. Windows Update is not working. When you click on check for updates it flashes for a second and then says there are no new updates available. In the windowsupdateclient event log there are windows update errors with the same 0x80070057 error that defender has.
windowsupdate.log:
2008-06-22 11:41:49:856 1056 b7c DtaStor FATAL: Bad parameter to function CSusEseSession:etServiceTransientInfo
2008-06-22 11:41:50:215 2752 b64 COMAPI FATAL: Unable to complete asynchronous search. (hr=80070057)
2008-06-22 11:41:50:856 1056 b7c DtaStor FATAL: Bad parameter to function CSusEseSession:etServiceTransientInfo
2008-06-22 11:41:51:028 2752 b64 COMAPI FATAL: Unable to complete asynchronous search. (hr=80070057)
2008-06-22 11:41:51:278 1056 b7c DtaStor FATAL: Bad parameter to function CSusEseSession:etServiceTransientInfo
2008-06-22 11:41:51:590 2752 b64 COMAPI FATAL: Unable to complete asynchronous search. (hr=80070057)
2008-06-22 13:18:55:785 1056 b64 DtaStor FATAL: Bad parameter to function CSusEseSession:etServiceTransientInfo
2008-06-22 13:18:56:259 2672 152c COMAPI FATAL: Unable to complete asynchronous search. (hr=80070057)
2008-06-22 13:19:33:129 1056 b64 DtaStor FATAL: Bad parameter to function CSusEseSession:etServiceTransientInfo
2008-06-22 13:19:33:254 2672 5c8 COMAPI FATAL: Unable to complete asynchronous search. (hr=80070057)
Can you please advise on how do I resolve this?
I have already tried the procedures you instructed in another thread Ronnie, but still, no luck.Sunday, June 22, 2008 6:14 AM -
Hi Ronnie,
I have this same problem with Vista Ultimate x64. I've tried the solution you have suggested but no change. My install was from the Technet ISO inclusive of SP1. I'm on the verge of scrubbing the system as it'as very unstable and I can't install updates to see if it can be improved. Any help greatly appreciated.
Cheers,
Jeff.Saturday, August 2, 2008 2:54 AM -
I am having the same issues with windows update. I have Vista ultimate x64 bit/SP1 downloaded as ISO from MSDN. I have reloaded this laptop from scratch a number of times early on trying to get Nvidia drivers working. Laptop is a Gateway FX. Here is what I am observing:
1) Windows update and Windows Ultimate Extras both say no new updates. In the Info box below it says:
Most Recent Check for updates: Today at 12:15 PMUpdates were installed: Never
When I check the View Update History is says you have never installed any updates.
3) I downloaded Windows6.0-KB952709-x64 , a hotfix released a few days ago. It refuses to install saying "The update does not apply to your system".
4) I have VS2008 installed and it installed SQL Express. I downloaded the Studio manager for x64 and installed it. None of the toolbars are there and I get on error on connect (unhandled expection in .net framework). I messed around with installing/uninstalling SQL express. Finally decided to remove it and install SQL 2005 Developer Edition. I pulled that off of MSDN yesterday and went through the whole setup of SQL 2005 and SP2. The studio manager there is doing the same thing. The error message from SQL Studio is
Description:5) This one may or may not be related. A download of anything from Firefox, results in a dialog of Microsoft C++ Runtime "Assertion Failed" . I can't read the exact location but it starts with d:/rtm/securityproducts... Line 979.
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: SqlWb.exe
Application Version: 2005.90.3042.0
Application Timestamp: 45cd69e0
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791941d
Exception Code: c0150015
Exception Offset: 0003c618
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
SQL Server is now generating this error:
2008-08-15 12:00:54.86 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2008-08-15 12:00:54.92 spid5s Error: 17311, Severity: 16, State: 1.
2008-08-15 12:00:54.92 spid5s SQL Server is terminating because of fatal exception 80000003. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
6) Starting Windows Sidebar always ends a unhandled exception. JIT using VS2008 says it triggered a breakpoint.
7) I figured I should probably check Windows Update after installing SQL and VS2008. That is when I noticed that nothing has been updated, ever. And that led me here to this forum.
Friday, August 15, 2008 5:46 PM -
Hi there,
Just an update for this group...
After extended email and phone conversations between myself and Microsoft support staff, (and having re-installed Vista Ultimate 64 from scratch again x 2) I did some further checking myself. It seems the technet build I had downloaded soon after SP1 was released was the 'checked/debug' version. I had [wrongly] assumed that this was a first release that incorporated SP1 and was labeled as such to indicate it had been tested and approved. I found info deep within the Microsoft 'vaults' (you try finding it on their site...!) that explained that this version is for software developers to test their drivers etc. and provides more debugging information... and runs a little slower.
So... I downloaded the Vista Ultimate 64 ISO again - making sure it was NOT the checked/debug version. Installed and... voila! All goood now and functioning 100%... at last.
Thought I'd post this in case it's the same problem for others. I did ask (suggest) to Microsoft that they put some sort of warning on technet...Tuesday, October 14, 2008 3:45 AM -
Jeff
Thanks for coming back letting us know how you resolved the problem.
Enjoy.
Ronnie Vernon
Microsoft MVP
Windows Desktop ExperienceWednesday, October 15, 2008 6:52 PMModerator