access violation error - Post ID 160686

User 106872 Photo


Registered User
92 posts

I recently dl/d HTML free editor. I opened up a index .htm page from a VSD site I'm working on. When I went to the code tab on the left I got an access violation error 77dad45f in module user32.dll address 000000004.
I clicked ok it came back a second time I clicked ok then it went away but came back another time later from a different entry point.
Do I need to reinstall.
System in athlon 1.7 ghz with 1 gig mem XP w/sp2 and enough HD room.
Thanks Wyndham
User 184085 Photo


Ambassador
1,707 posts

There should have been an update awhile ago to XP to fix this, try updating XP to see if it clears up.
Volunteering to help :)
http://www.tbaygeek.ca
My HTML play area
http://www.tbaygeek.ca/test/
User 122279 Photo


Senior Advisor
14,624 posts
Online Now

Wyndham, you'd better download and install SP3 for winxp.
Ha en riktig god dag!
Inger, Norway

My work in progress:
Components for Site Designer and the HTML Editor: https://mock-up.coffeecup.com


User 500110 Photo


Registered User
5 posts

I am also seeing the same access violation error (user32.dll) with build 369 (paid) that I installed about a week ago on windows XP pro SP3. I installed over build 305 witch was originally installed when the OS was SP2. My system, as far as I know, is all up to date via Microsoft’s auto updates. Do you have Microsoft’s KB number for the update that should fix this?

Thanks

A
User 103173 Photo


VP of Software Development
0 posts

Amepro wrote:
I am also seeing the same access violation error (user32.dll) with build 369 (paid) that I installed about a week ago on windows XP pro SP3. I installed over build 305 witch was originally installed when the OS was SP2. My system, as far as I know, is all up to date via Microsoft’s auto updates. Do you have Microsoft’s KB number for the update that should fix this?

Thanks

A

Here is a KB article from Microsoft that may help:

http://support.microsoft.com/kb/142676
Learn the essentials with these quick tips for Responsive Site Designer, Responsive Email Designer, Foundation Framer, and the new Bootstrap Builder. You'll be making awesome, code-free responsive websites and newsletters like a boss.
User 500110 Photo


Registered User
5 posts

Thanks Scott, I’ll peruse the information and keep you posted. In the mean time I found that if I open a document, click on the side “Code” tab, dismiss the two error pop-ups and then toggle to “Visual Editor”, every thing works as long as I don’t shut down the CC HTML Editor. If I do restart, I have to repeat the process. This seems to work if the initial document mode is set to HTML. If initial document mode is WYSIWYG, the pop-ups keep coming back, does not seem to stop.

I also found two updates on Microsoft web site that for some reason never came through the automatic updates. These updates are for Visual C++ 2005 SP1 (kb2467175) and Visual C++ 2008 SP1 (kb2467174). I’ll let you know if they make a difference after installation.

A
User 500110 Photo


Registered User
5 posts

Sorry for not posting back sooner, busy few days. My computer now has no outstanding high-priority updates (as per Microsoft Update website), but the user32.dll error is still occurring only with CC HTML editor. However, with the work around mentioned in my earlier post, everything seems to be working fine, so I’ll live with it for now until the next Editor update when I’ll do a clean install.

Does anyone know if the fix might be one of the optional updates?

Thanks,

A
User 629005 Photo


Ambassador
2,174 posts

Here's an article from Microsoft Support that discusses this error and most probable solutions. Read it over and try the two tasks listed. I will say that if you delete CC HTML Editor, I'd run CCleaner afterwards.

http://support.microsoft.com/kb/142676

Here's a link to CCleaner: http://www.piriform.com/ccleaner/download

As far as updates to Winders... I install them all, high priority, mandatory, optional, suggested, doesn't matter. I figure I paid good money for the darned OS, least I can get out of them is the updates, even if they don't fix everything ;)

Edit: Ooops, didn't realize that was the same article that Scott referenced. STILL, I'd read through that and try what they suggest.
Living the dream, stocking the cream :D

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.