Reply to post: Re: Registry, ugh

Happy birthday Windows 3.1, aka 'the one that Visual Basic kept crashing on'

CommonBloke

Re: Registry, ugh

It was user error, I did something which triggered a registry change for every executable, or a registry change to how WinExplorer treated .exe. What I did that caused that, I don't remember, but the fact that the only way to fix it was by downloading a registry changing script and praying it wouldn't bork my machine further shows how problematic the whole thing is when it's borked.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon