Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > Still having auto-update problems?

Reply
Thread Tools Display Modes

Still having auto-update problems?

 
 
Epsilon
Guest
Posts: n/a

 
      11-26-2006
I tried all methods to get the auto-updates working again, following the
various threads and liaising with Microsoft directly, with no success. What
I did discover was that when trying to re-register the file qmgr.dll I was
getting the message "loadlibrary("qmgl.dll") failed - invalid access to
memory location" (all other files re-registered without a problem). When I
searched for the qmgl.dll file I discovered 2 versions, one in the System32
folder and another in the System32/bits folder, both with different dates. I
copied the older version and pasted over the newer variant and auto-update
operation resumed immediately.

So if you've tried and failed check the qmgl.dll file details.
 
Reply With Quote
 
 
 
 
Stu
Guest
Posts: n/a

 
      11-26-2006
Hi Epsilon

You say you have tried all methods but not what you have tried so far -
there are many reasons why WU won`t work. Often the problem is with the
Microsoft XML Parser which you need for WU to work. Have you tried
re-registering the DLLs for the Parser? If not, try this:

Open command window Start>Run>CMD then type in these commands and hit Enter
after each one. You must wait for a message indicating each one has succeeded
before proceeding to the next.

REGSVR32 C:\WINDOWS\SYSTEM\MSXML.DLL
REGSVR32 C:\WINDOWS\SYSTEM\MSXML2.DLL
REGSVR32 C:\WINDOWS\SYSTEM\MSXML3.DLL

Let me know how it works out

Stu


"Epsilon" wrote:

> I tried all methods to get the auto-updates working again, following the
> various threads and liaising with Microsoft directly, with no success. What
> I did discover was that when trying to re-register the file qmgr.dll I was
> getting the message "loadlibrary("qmgl.dll") failed - invalid access to
> memory location" (all other files re-registered without a problem). When I
> searched for the qmgl.dll file I discovered 2 versions, one in the System32
> folder and another in the System32/bits folder, both with different dates. I
> copied the older version and pasted over the newer variant and auto-update
> operation resumed immediately.
>
> So if you've tried and failed check the qmgl.dll file details.

 
Reply With Quote
 
Stu
Guest
Posts: n/a

 
      11-26-2006
BTW I`m assuming you have the BITS service started. Star>Run type
"services.msc" (without the quotes) then navigate to Background Intelligent
Transfer Service - ensuring it `s status is Started.

Stu

"Stu" wrote:

> Hi Epsilon
>
> You say you have tried all methods but not what you have tried so far -
> there are many reasons why WU won`t work. Often the problem is with the
> Microsoft XML Parser which you need for WU to work. Have you tried
> re-registering the DLLs for the Parser? If not, try this:
>
> Open command window Start>Run>CMD then type in these commands and hit Enter
> after each one. You must wait for a message indicating each one has succeeded
> before proceeding to the next.
>
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML.DLL
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML2.DLL
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML3.DLL
>
> Let me know how it works out
>
> Stu
>
>
> "Epsilon" wrote:
>
> > I tried all methods to get the auto-updates working again, following the
> > various threads and liaising with Microsoft directly, with no success. What
> > I did discover was that when trying to re-register the file qmgr.dll I was
> > getting the message "loadlibrary("qmgl.dll") failed - invalid access to
> > memory location" (all other files re-registered without a problem). When I
> > searched for the qmgl.dll file I discovered 2 versions, one in the System32
> > folder and another in the System32/bits folder, both with different dates. I
> > copied the older version and pasted over the newer variant and auto-update
> > operation resumed immediately.
> >
> > So if you've tried and failed check the qmgl.dll file details.

 
Reply With Quote
 
Epsilon
Guest
Posts: n/a

 
      11-26-2006
Stu,

As you say, there can be many reasons why things don't work but I reckoned
that enough fixes were already listed on this forum for people to look at
without me duplicating other posts, and reverting to the older version of the
file on my system was not covered in any previous posts but did the trick and
everything now works ok (for me). All backlogged updates (around 44 of them)
downloaded and installed without a hitch, and I was then able to install IE7.


"Stu" wrote:

> Hi Epsilon
>
> You say you have tried all methods but not what you have tried so far -
> there are many reasons why WU won`t work. Often the problem is with the
> Microsoft XML Parser which you need for WU to work. Have you tried
> re-registering the DLLs for the Parser? If not, try this:
>
> Open command window Start>Run>CMD then type in these commands and hit Enter
> after each one. You must wait for a message indicating each one has succeeded
> before proceeding to the next.
>
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML.DLL
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML2.DLL
> REGSVR32 C:\WINDOWS\SYSTEM\MSXML3.DLL
>
> Let me know how it works out
>
> Stu
>
>
> "Epsilon" wrote:
>
> > I tried all methods to get the auto-updates working again, following the
> > various threads and liaising with Microsoft directly, with no success. What
> > I did discover was that when trying to re-register the file qmgr.dll I was
> > getting the message "loadlibrary("qmgl.dll") failed - invalid access to
> > memory location" (all other files re-registered without a problem). When I
> > searched for the qmgl.dll file I discovered 2 versions, one in the System32
> > folder and another in the System32/bits folder, both with different dates. I
> > copied the older version and pasted over the newer variant and auto-update
> > operation resumed immediately.
> >
> > So if you've tried and failed check the qmgl.dll file details.

 
Reply With Quote
 
Epsilon
Guest
Posts: n/a

 
      11-26-2006
Stu,

The final fix I tried before 'stumbling' across the qmgr.dll version
discrepancy was as follows. The update package in step 1 failed with a
message that I already had a newer version on my system, following the same
thread on how to check the dll file versions led me to finding the two
locations as mentioned in my initial post:

Suggestion:
*************
Step 1:
Verify that the latest version of the BITS is installed by verifying the
version of files documented in knowledge base article 842773 - "An update
package that includes BITS 2.0 and WinHTTP 5.1 is available" at
<http://support.microsoft.com/?id=842773>


Step 2:
Reregister the Qmgr.dll and Qmgrprxy.dll BITS files. To do so, follow these
steps:

Click Start, click Run, type regsvr32 qmgr.dll in the Open box, and then
click OK.

Click OK again.

Click Start, click Run, type regsvr32 qmgrprxy.dll in the Open box, and then
click

OK. Click OK again.


Regards

Epsilon

"Epsilon" wrote:

> Stu,
>
> As you say, there can be many reasons why things don't work but I reckoned
> that enough fixes were already listed on this forum for people to look at
> without me duplicating other posts, and reverting to the older version of the
> file on my system was not covered in any previous posts but did the trick and
> everything now works ok (for me). All backlogged updates (around 44 of them)
> downloaded and installed without a hitch, and I was then able to install IE7.
>
>
> "Stu" wrote:
>
> > Hi Epsilon
> >
> > You say you have tried all methods but not what you have tried so far -
> > there are many reasons why WU won`t work. Often the problem is with the
> > Microsoft XML Parser which you need for WU to work. Have you tried
> > re-registering the DLLs for the Parser? If not, try this:
> >
> > Open command window Start>Run>CMD then type in these commands and hit Enter
> > after each one. You must wait for a message indicating each one has succeeded
> > before proceeding to the next.
> >
> > REGSVR32 C:\WINDOWS\SYSTEM\MSXML.DLL
> > REGSVR32 C:\WINDOWS\SYSTEM\MSXML2.DLL
> > REGSVR32 C:\WINDOWS\SYSTEM\MSXML3.DLL
> >
> > Let me know how it works out
> >
> > Stu
> >
> >
> > "Epsilon" wrote:
> >
> > > I tried all methods to get the auto-updates working again, following the
> > > various threads and liaising with Microsoft directly, with no success. What
> > > I did discover was that when trying to re-register the file qmgr.dll I was
> > > getting the message "loadlibrary("qmgl.dll") failed - invalid access to
> > > memory location" (all other files re-registered without a problem). When I
> > > searched for the qmgl.dll file I discovered 2 versions, one in the System32
> > > folder and another in the System32/bits folder, both with different dates. I
> > > copied the older version and pasted over the newer variant and auto-update
> > > operation resumed immediately.
> > >
> > > So if you've tried and failed check the qmgl.dll file details.

 
Reply With Quote
 
MikeC
Guest
Posts: n/a

 
      11-26-2006
Epsilon wrote:
> I tried all methods to get the auto-updates working again, following the
> various threads and liaising with Microsoft directly, with no success. What
> I did discover was that when trying to re-register the file qmgr.dll I was
> getting the message "loadlibrary("qmgl.dll") failed - invalid access to
> memory location" (all other files re-registered without a problem). When I
> searched for the qmgl.dll file I discovered 2 versions, one in the System32
> folder and another in the System32/bits folder, both with different dates. I
> copied the older version and pasted over the newer variant and auto-update
> operation resumed immediately.
>
> So if you've tried and failed check the qmgl.dll file details.

Below in this ng sorted by date descending, I twice posted a topic with
the following contents which received the exact same reply but my repost
included the update that the first suggestion was not effective. Do you
[think] your solution may help then with:

[pasted begins]

I am pasting the contents of my previous thread (short enough anyway).
The problem persists. I further Googled for the hexadecimal error
number. There are a number of Google hits to Experts-Exchange and I am
wondering if it is worth buying the answer?

Again, I am stuck in a loop where each update attempt fails with the
"You must reboot your computer..." and the hex number 0x8DDD0007.

What may be the cause is a poorly applied in-place upgrade that [was]
intended to remedy a virus (not my solution) and using the previous
Windows 2000 Professional "WINNT" directory. The previous solution
provider asserted some system files were damaged and thus the problem.
He gave up and returned the PC.

[pasted ends]

TIA,

MikeC
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows Vista Auto Update Suspended (Due 2 Lots Of Problems With It). Windows Vista General Discussion 2 02-21-2008 01:38 PM
latest Vista auto. update caused problems Keepitout Windows Vista General Discussion 0 01-20-2008 03:36 PM
Auto windows xp update and re-starting problems DPI12 Windows Update 0 08-12-2005 09:04 PM
Problems after auto update-beta scan Wally Windows Update 3 04-17-2005 07:40 PM
Auto update download problems Seamus F Windows Update 4 12-18-2004 05:12 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59