Windows 10: AcGenral.dll causing Word to crash

I hope I am posting this in the right place. I just did the GWX thing and most things work as expected. They say old dogs like me can't learn new tricks. That's not true, we just don't want to. I tell you that because I am still using MS Office 2003. In general it works ok but if I open a word doc and then open a webpage and copy unformated text I can paste it in word. BUT if I copy text from a page that is using columns or frames and try to paste it word immediately crashes. Here is the event log for the failure.

Faulting application name: WINWORD.EXE, version: 11.0.8411.0, time stamp: 0x532a603f
Faulting module name: AcGenral.DLL, version: 10.0.10586.17, time stamp: 0x56518c44
Exception code: 0xc0000005
Fault offset: 0x000307a2
Faulting process id: 0x880
Faulting application start time: 0x01d180949bb82c7f
Faulting application path: C:\Program Files (x86)\Microsoft Office\OFFICE11\WINWORD.EXE
Faulting module path: C:\WINDOWS\AppPatch\AcGenral.DLL
Report Id: fed6baa7-ec87-11e5-bdc7-001fd0a247a8
Faulting package full name:
Faulting package-relative application ID:

I tracked down AcGenral.dll
(x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_10.0.10586.17_none_33f35d9feabbba0e)
and I notice that it is a newer version. I did not want to do anything until I picked your collective experience.

First question is "is AcGenral.dll the problem?
Should I replace AcGenral.dll with the older version?
How would I do this? Take Ownership, unlock and replace?
Perhaps try to install the old .dll (copy & register) in System32. Would Word find it first?

Can anyone duplicate this problem with Office 2007 or later? Again, try to copy an article using columns and or frames and paste it into Word,

Thanks from the newbee
Steve

:)

 

GPUpdate causes Word 2016 to crash.

I found a work around for my problem. I haven't solved the underlying problem, but at this point I just need it to go away.

I did some isolation through the process of elimination. The issue either involves printer drivers or the Group Policy Object (GPO) that handles connecting network printers and runs in the back ground about every two hours. I upgraded
all the printer drivers for 96 printers. Luckily there are only about six different printer models and nearly all of them can use the HP universal printer driver.

Since upgrading all the drivers made zero impact I suspect the issue surrounds the GPO removing all network printers and reinstalling based on the computer name or username / group membership. I don't feel it is a printer driver issue.
Instead I feel it is related to the drivers getting removed and reinstalled, but I can't prove it. I need to refresh the installed printers because we have a large number of roaming users, but it only needs to occur once at logon. It doesn't need to reoccur
every time the GPOs are refreshed. That leads to my work around.

I abandoned the idea of using a GPO to connect printers in favor of a logon script. I prefer the GPO preference to connect printers, but again, I need to be done with this issue. So, the login script functionally does exactly what the
GPO does, such as removing all the existing network printers then reconnecting based on computer and user. However, the logon script only runs once at logon then it is done.

In summary, I ditched connecting network printers through a group policy object in favor of a logon script.

 

GPUpdate causes Word 2016 to crash.

Hi,

For better assistance, please post your question to
TechNet.

Thanks.

 

2003 is no longer supported, so it does not surprise me. 2007 is also no longer supported. You need to run 2010 or 2013.