Windows Update KB4048955 may be the MED killer
I'm uninstalling some Windows updates because my sound drivers are affected badly, but I also found NL mission editors were crashing on start.
I randomly selected an update to uninstall, but I forgot to note which one it was 'cause my 'genius' is severely limited. After the reboot, I tried to start a MED and it went fine. Attempting to figure out the designation of the MED killing update, I noticed that Windows update KB4048955 is now waiting to be installed, so I'm assuming that's the one I just uninstalled. I'm asking lolfake or stompem or anybody that can't get the MED to start to uninstall Windows update KB4048955 and report the results. Thanks! Edit: So immediately after uninstalling my sound drivers to attempt reinstalling them to see if they work correctly again, I had to reboot, during which KB4048955 reinstalled itself. After, I abandoned working the sound driver and uninstalled KB4048955 again and KB4055237 as well, thinking I'll figure out how to block them after, and after rebooting, found I have no access to them at all now, and KB4504022 has no deinstall option, and the MEDs won't start again. I'm livid. |
Hi Baldo, we meet again at this point. IE somehow I remember having to solve a similar problem in windows 7 and 8 although this is an unsolvable one at present.
I think it's part of the creator update but it may not be permanent. So in the mean time the solution I've come up with is a Virtual OS running XP. You'll need an XP or win7 - 8 disk and a virtual machine software solution. Run the MEd from there then backup to a shared USB. :dontknow: :dontknow: :dontknow: :dontknow: :dontknow: :dontknow: :dontknow: :dontknow: |
I hate this planet.
I'm having more or less consistent luck with this trick:
If a MED fails to start, repeat the steps again. Give it a try, buddy. Reports of success and/or failure will be highly appreciated. |
I had a similar experience where it worked, then it worked only whilst the settings applet was open, then not at all.
So I tried adding legacy DLLs to the game root, d3d8.dll worked but about the time it took to have a cup of coffee and celebrate finding a fix, it was all busted again. I suspected a problem with the compatibility settings holding, I even suspected sabotage from the system itself or the antivirus etc. I've run every scenario I can think of... |
Hey wow,
I have to say I'm damn too lucky as after my creator update that everything is just fine. And I'LL respond to you again when I'm in my office. Good luck. |
@Baldo
I'm currently investigating another possible cause. My system has the latest Nvidia TI graphics system and drivers. Could be... I was running AMD GFX and drivers in the retired Windows 8.1 system. Worth considering because I was getting various interesting responses from different directx drivers I tried yesterday. |
@lolfake
Thanks for the info it helps. Now I know it's not just me because Baldo has the same problem (though slightly different) and you are apparently unaffected. This indicates a temporary situation. |
My med opens as long as I set the compatibility to "XP". Otherwise, it crashes. I don't have a nVidia card either and I do have the latest updates.
Probably a window drawing issue with the new update. |
Actually I have two PC's with different Windows 10 at home I've got Windows 10 Professional at work Windows Server 2016 which is same as the Windows 10 at work its working fine but at home I discovered some issues before but I fixed them.
|
I forgot to tell you I have Nvidia Gtx 1060 just in case you need to know 'detective'.
|
FIXED
The security system and hardware monitor have been blocking any changes, even new drivers would not hold. MMM... Fixed it by forcing UAC to let me give administrator permission for the drivers to go in. Here's the script, it can be modified to work with any programs that need to get admin permission in Windows 10 when you can't do it from the desktop, modify filenames, paths and executable names as needed. Code:
@echo off |
Quote:
I get it randomly or after a reboot - if it won't start during the session, then another reboot fixes it for that session, until you reboot, then it may or may not do it again..... :thud: |
Sorry but you all are goners from the MED don't know why?
|
Quote:
If you read what was said, we simply worked around it. |
Quote:
Just an unsolvable origin for now. Thank you for your support |
Quote:
|
Quote:
Once again thanks for your support but the case is closed for me. If you're having problems with Windows 10 try Baldo's method... Quote:
|
You all have Windows 10 Home or Professional?
|
I have Windows 10 Home.
And even messing around with compatibilty settings, starting any MED is unreliable. Sometimes it takes dozens of attempts. I'm so frustrated. Just now tested for fun: Every single MED start attempt worked on the first simple double-click. DFWIQ MED, TIOCoop MEDs (consumer and unlocked), both C4 MEDs (consumer and unlocked). No muss, no fuss. I hate it when things don't function, but I REALLY HATE it when they start functioning again and I HAVE NO IDEA WHY! I'm losing my mind... |
Quote:
NOPE not with the Creator update and Nvidia drivers. Finally I found a solid Asus Laptop with windows 10 Pro installed it was still sitting on a shelf in the local pawn shop. The OS was digitally installed by the pawn shop before the creator update, I managed to sneek onto the net while windows wasn't watching to activate DFX2 and all is fine. |
All times are GMT -5. The time now is 07:17 AM. |
Powered by vBulletin®