InterLinked

Yeah, I still haven't been able to get mpam-fe64.exe to do anything of late... this might be something weird going on actually, I don't know what, exactly, but it's possible others with MSE are also having similar issues. I don't actually have MSE installed on my W7, just Defender (native), and that updated its definitions fine when I told it to. Seems something Vista-related is going on.

I just manually installed 2 days ago so unless something has changed since then, that works great.

I manually install the definitions, though I don't do it everyday, only now and then. I installed definitions 2 days ago so my MSE right now is still happy about that. What's weird is Vista 64-bit definitions are now called mpas-fe.exe... typo on Microsoft's part?? It's also only half the size of the previous mpam-fe64 that I had. I do indeed get the same error described when trying to auto-update in MSE. I haven't tried auto-updating MSE at all recently on any OS except W7 where it still works AFAIK. This is the other link I had for definition updates, which is the one I used last time, which gives me a 107 MB mpam-feX64 for 64-bit: https://support.microsoft.com/en-us/help/971606/how-to-manually-download-the-latest-definition-updates-for-microsoft-s It is slightly larger (about 1 MB) than the one I installed 2 days ago, which was about 106MB. Having some difficulty trying to get it to run but I've been having trouble getting pretty much everything to run lately on there so I won't give up yet. Eventually, it might work.

As Ben said, it's purely cosmetic. I know it's not adequate; I just wanted to do it because I can. I don't run any antivirus at all on Windows 2000 and haven't had any issues, so XP + MSE seems like a decent combo to me. I'll never be able to update MSE again, so why be updated with its colors? I thought Windows 10 Defender was annoying, but I was on Vista the other day and extracted a 7Z file from MSFN and MSE 4.4.304 promptly removed the files.... guess it's trying to send me a message

Thanks, @VistaLover - this really clears a lot of things up, even though I did manage to get somewhere at last. Eventually, I figured out that mpam-fe.exe was no longer compatible with XP as you said and my attempts to extract MpSigStub and all that failed as well. I ended up finding the last compatible mpam-fe.exe (~475 days old now) and running that. Old, but better than nothing. I'm not kidding myself that this is adequate for XP, but it's better than nothing, I figured. Now, my MSE is yellow instead of red - sometimes, it's even green! No issues at all on Vista. I have 4.4.304 there and manually running the definition worked well.

I tried a portable version of Iron 70 just now and that does not seem to like me, either. So only a portable version of a specific Chromium browser is working, but no other Chromium browsers like Chrome/Iron are working?

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.

How have people here been installing Chrome? I've been trying to install SRWare Iron 70 and not been having any luck. Ditto for Chrome 70. I'm wondering if there's a simpler way than trying to use Application Verifier on a trace of files. Maybe not possible but how are people installing their programs exactly?

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...

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.

I just used e42 for 10 years instead of 1 or 2 My MSE is green right now, after a reboot, so we'll see if it goes yellow again. If/when it does, I'll just run this reg script!

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. Those were the only 2 I saw The odd thing is Dependency Walker doesn't even show dssenh as a loaded DLL...

Yup, no difference, even with both set to 0 Thoughts on system32? What's the downside of that?

@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?

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?

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?

What happens if you run Dependency Walker on winword.exe? @Dave-H I don't see it loading dssenh.dll at all for me there, do you?

Unfortunately, I don't see it there

@daniel_k @Dave-H Do I need to enable DLL redirection or something, so it uses the DLL in Office14, not system32? It's still broken for me unless I replace the system32 copy

Did you have to reboot? it didn't work after I copied it in there once the system file was back EDIT: I rebooted and it's still broken... ?

Whoops, I replaced the system32 one Let me change it back! Office worked with that, but who knows what else that could've broken... better to do it that way!

Used Replacer, it works! Thanks @daniel_k - this is great!

Were you able to do an online, live replace? Seems Replacer might be required here...

Hey, that's awesome! Seems like I already downloaded that, let me see if I have that. So installing the update isn't enough, a manual DLL override is required?

Turns out you CAN have your cake and eat it too, actually: Thanks to @daniel_k for figuring this out: Get KB3081320 from WU Catalog, extract it and copy dssenh.dll to C:\Program Files\Microsoft Office\Office14. If that doesn't work, copy it into system32 using Replacer and reboot