Probs with KB925902 *NOT* Realtek

[Wigster]

Hi,

Installed the KB925902 patch this morning. Now every time I run Matlab
2007a, I get the same error that people are getting with the Realtek
control panel.

startdir.EXE Illegal System DLL relocation
The system DLL user 32.dll was relocated in memory....etc.

(strictly speaking it is the startdir.exe file which launches Matlab that
is causing the error, so I can circumvent it, thankfully)

I have installed the Realtek patch that came out today (KB935448), but this
hasn't solved the problem.

I also seem to get the same issue with the setup executable for ghostscript
8.56.

Does anyone have any suggestions?

Thanks.

 

[Guest]

The KB 935448 article suggests that if you are getting similar issues, you
should contact Microsoft Support. They can assist you to resolve things.

Best Wishes,
Kurosh

 

[Skeats]

The KB 935448 article suggests that if you are getting similar issues, you
should contact Microsoft Support. They can assist you to resolve things.

Best Wishes,
Kurosh

I got the same message when trying to use my TUGzip program and on Googling
the whole statement I found forums that had as many as 40 complaints
already.

I uninstalled the last update of 3rd April 2007 and now my unzipping works
properly. (I had put the install/uninstall programs into "date last used
order" to find the last update).

I am awaiting a revised update from Microsoft and possibly an apology?

Skeats

 

[Guest]

I uninstalled the last update of 3rd April 2007 and now my unzipping works
properly. (I had put the install/uninstall programs into "date last used
order" to find the last update).

I am awaiting a revised update from Microsoft and possibly an apology?

Skeats

Hi Skeats,

Yes, uninstalling the new update is one workaround. However, to get a
proper resolution (considering that the update is meant to make your computer
more secure, which is a good thing) you should also contact Microsoft. They
won't charge you (or will offer a refund) if / when they determine that their
update is the cause of the problem.

There are hundreds / thousands of potential conflicts whenever software is
changed. No doubt they are balancing how fast they have to get an update out
to everyone (this was a "critical update", otherwise it would have come out
with the rest of the monthly updates) with how stable the update is. With
feedback from people who are having problems (like yourself), they will be
able to provide a more stable update faster. If they waited until they were
sure the update was completely stable (which is pretty much impossible -- all
software goes through updates to make them more stable and secure), no doubt
many people would be complaining to them about the security risk their
computers had without the update, or how their computers were compromised
without it. Don't expect an apology; be part of the solution.

Best Wishes,
Kurosh

 

[Guest]

Also, did you try installing the patch (KB 935488)? It is not known to
correct your specific issue, but Microsoft does mention that similar issues
may be corrected with this patch. If it does resolve things, you should also
let them know, so they update the article with that information.

Best Wishes,
Kurosh

 

[Skeats]

Also, did you try installing the patch (KB 935488)? It is not known to
correct your specific issue, but Microsoft does mention that similar
issues
may be corrected with this patch. If it does resolve things, you should
also
let them know, so they update the article with that information.

Best Wishes,
Kurosh

I'll have a look at that.
I did use the feedback option to Microsoft when I found an article on their
help site that was similar.

Thanks.
Skeats

 

[Rock]

Nicely said.
--
Rock [MS-MVP User/Shell]

Hi Skeats,

Yes, uninstalling the new update is one workaround. However, to get a
proper resolution (considering that the update is meant to make your
computer
more secure, which is a good thing) you should also contact Microsoft.
They
won't charge you (or will offer a refund) if / when they determine that
their
update is the cause of the problem.

There are hundreds / thousands of potential conflicts whenever software is
changed. No doubt they are balancing how fast they have to get an update
out
to everyone (this was a "critical update", otherwise it would have come
out
with the rest of the monthly updates) with how stable the update is. With
feedback from people who are having problems (like yourself), they will be
able to provide a more stable update faster. If they waited until they
were
sure the update was completely stable (which is pretty much impossible --
all
software goes through updates to make them more stable and secure), no
doubt
many people would be complaining to them about the security risk their
computers had without the update, or how their computers were compromised
without it. Don't expect an apology; be part of the solution.

 

[Wigster]

Just wanted to add that the user32.dll memory conflict after installing
KB925902 is also present with MikTeX.

You get the error and can not Texify your text file.

Installing the Realtec patch does not help.

Iggy

 

[Guest]

Hi Iggy,

Best thing to do is contact Microsoft directly to let them know. They may
be able to help you resolve that.

Best Wishes,
Kurosh

 

[Wigster]

Hi,

Installed the KB925902 patch this morning. Now every time I run Matlab
2007a, I get the same error that people are getting with the Realtek
control panel.

Turns out it is a conflict with the Vista Inspirat Brico Pack. I have
uninstalled that and everything works.

 

[Guest]

Turns out it is a conflict with the Vista Inspirat Brico Pack. I have
uninstalled that and everything works.

Hi Iggy,

Thanks for the update. How did you determine this was the cause? I did a
quick Google search, and found nothing relating the two.

Best Wishes,
Kurosh

 

[Wigster]

Hi Iggy,

Thanks for the update. How did you determine this was the cause? I
did a quick Google search, and found nothing relating the two.

Someone mentioned that shell32.dll is responsible for the theme information
for Explorer and this was the only nonstandard theme pack that was
installed on my machine.

It seems that there is some talk of this on the crystalxp.net fora now.

 

[Guest]

Someone mentioned that shell32.dll is responsible for the theme information
for Explorer and this was the only nonstandard theme pack that was
installed on my machine.

It seems that there is some talk of this on the crystalxp.net fora now.

Okay, thanks. The original message you posted said the error was with
"user32.dll" (which is what appears with the Realtek problem), not
"shell32.dll" -- that's probably why we couldn't link the two.

Best Wishes,
Kurosh

 

[PA Bear]

Okay, thanks. The original message you posted said the error was with
"user32.dll" (which is what appears with the Realtek problem), not
"shell32.dll" -- that's probably why we couldn't link the two.

The Known Issues section of KB925902 was updated on 06 Apr-07. See
http://blogs.technet.com/msrc/archi...ft-knowledge-base-article-925902-updated.aspx
for some important information.

 

[Ottmar Freudenberger]

Okay, thanks. The original message you posted said the error was with
"user32.dll" (which is what appears with the Realtek problem), not
"shell32.dll"

Ehm, the error message mentions _both_ DLLs. In case you see one
including "system32.dll", the cause for the error message is most
likely an design changing third party Theme or "Transitional Pack"
(like those "BricoPacks") you've installed on your machine.
Uninstalling those design changeing applications will result in
a Windows XP looking like Windows XP and not crashing any longer
while starting an application. Installing KB935448 does *not* help
in those cases.

In case you see error messages mentioning "hhctrl.ocx", then instal-
ling KB935448 will most likely stop these error messages.

FWIW,
Freu"MSRC has been informed about the system32.dll error messages
and the cause of these"di