As a thought - is your master database valid (ie not corrupt) prior to installing that update? I would run checkdb on it and verify that it is valid as it COULD be the database is corrupt.
Now, when you say "corrupt", what is the EXACT error message you are getting? I've seen cases where an update caused odd problems on my side, but it was due to our failover software not behaving like I expected during the upgrade and it caused some logins to lose permissions on master. I was able to recover but it took me a little bit to figure things out.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.