Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Beware of Office 2010 Updates!


 Share

Recommended Posts

15 minutes ago, daniel_k said:

@Dylan Cruz

I have no idea what is going wrong on your system.
I've just copied dssenh.dll to the Office folder. That's all.

I'm wondering if it's because I have SP4 and all that or not,

Do you have all of the POS updates and everything?

Link to comment
Share on other sites


6 minutes ago, daniel_k said:

@Dylan Cruz

Pretty sure you have a CWDIllegalInDllSearch registry entry.
http://web.archive.org/web/20141212220002/support.microsoft.com/kb/2264107

Probably
it was added to SP4, as it isn't enabled by default.

Checking now... if I have it, can I just delete it?

UPDATE: Mine is set to "1"

- 1 (Blocks a DLL Load from the current working directory if the current working directory is set to a WebDAV folder)

Office14 isn't a WebDav folder, so I'm not sure what the deal is here...

Even when set to 0, I still have the issue so this doesn't seem related?

Edited by Dylan Cruz
Link to comment
Share on other sites

@daniel_k

Changed another related reg setting I saw there, no effect.

At this point, I'm wondering if it would be best to just go back and replace the system32 one. Obviously the Office14 way is simpler if it works, but since it's not, is there any real downside you can see to replacing the system32 one?

Link to comment
Share on other sites

1 minute ago, Dylan Cruz said:

Thoughts on system32? What's the downside of that?

You need to do some tests.
I'm not sure if that DLL is also used for connection purposes or local encryption only.

In the mean time, I would search for any other registry setting that changes DLL search path.

Link to comment
Share on other sites

Just now, daniel_k said:

You need to do some tests.

 

I did earlier and things SEEMED to work with the system32 one replaced,

THen again I have no idea what this DLL file does or what programs use it.

 

Just now, daniel_k said:


I'm not sure if that DLL is also used for connection purposes or local encryption only.

In the mean time, I would search for any other registry setting that changes DLL search path.

Those were the only 2 I saw

The odd thing is Dependency Walker doesn't even show dssenh as a loaded DLL...

Link to comment
Share on other sites

Quote

To enable DLL redirection machine-wide, you must create a new registry key. Create a new DWORD key called DevOverrideEnable at HKLM\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options and set it to 1. After this, you must restart your computer to see the effects.

https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-redirection

Just like the thing I did to fix SHA-2 encryption in Office 2007 in Windows 2000, you can create a *.exe.local file for each office application and copy dssenh.dll to the office14 directory, along with possibly older versions of crypt32.dll, schannel.dll and rsaenh.dll.

  • Upvote 1
Link to comment
Share on other sites

1 minute ago, win32 said:

you can create a *.exe.local file for each office application

What is this file supposed to be exactly?

Just copy winword.exe for instance and name it winword.exe.local ? (+Repeat for excel and powerpnt?)

I've already got dssenh.dll in the office14 dir.

Link to comment
Share on other sites

1 minute ago, Dylan Cruz said:

What is this file supposed to be exactly?

Just copy winword.exe for instance and name it winword.exe.local ? (+Repeat for excel and powerpnt?)

It can be anything. Just make a new text document and rename it to winword.exe.local. and yes, repeat.

Link to comment
Share on other sites

1 minute ago, win32 said:

It can be anything. Just make a new text document and rename it to winword.exe.local. and yes, repeat.

Unfortunately, it still doesn't work with a winword.exe.local and dssenh.dll in there,

It's odd that others have not had this issue though, which seems rather bizarre.

Would it be prudent to just replace the system32 one or keep trying to find a different way? My Dependency Walker didn't show dssenh.dll at all, but neither did Dave's and his works...

Link to comment
Share on other sites

OK, I gave up, since I wasn't getting anywhere with this - I replaced the system32 version and all is well again.

I will play around and see if the stability of anything else is adversely affected, though my guess is it probably doesn't matter at all.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...