The reset got me started again and then four hours after I attempted Microsoft help desk they called me back (read: 2 hours after the 2 hour estimated wait time) to see what I needed. Create a Windows 10 boot media with a zip drive on my wife's computer and use it to reset Windows on mine. Nope, Windows 10 boots too fast for that.Įventually I found an answer. Nope, Windows launching crashed into a dead black screen.
I was able to find a video explaining how to get control of the system32 folder which may have helped me fix things but the video went black and my computer died. Hurray! Except now it wouldn't go back into the system32 folder and I kept noticing new Windows functions that weren't working anymore. So I took it out and was able to rename it. "That's strange," I thought to myself again, "I wonder if it will change if I take it out of the system32 folder." Detlef Riekenberg (3): user32/tests: Avoid crash on win9x. So I went back to rename the file but it wouldn't rename. Andrew Nguyen (1): winmm: Fix a potential infinite recursion bug. "Oh shoot," I thought to myself, "the system32 winmm.dll must have been important to run Windows! I better go and change it back." Actually, nothing was working except for basic open / close folders. Ive been running with the same mods for many hours and it has been pretty stable. CTDs happen on previous saves where before it wasnt a problem. Spoiler randorandington wrote: Hi All,I recently had severe and reproducible CTDs when entering/exiting power armor or raising my weapon in Far Harbor/The Nucleus. Then I spied the correct winmm.dll file and renamed it but Settlers 3 still didn't work. of 858 - Buffout 4 - posted in File topics: In response to post 100104553. Nothing bad happened at first and Settlers 3 still didn't work. So I found out how to bypass the security in the system32 folder and renamed the winmm.dll file. you are not going to believe what happened to me.