maniac Posted March 11, 2010 Author Posted March 11, 2010 Solved this in the end, purely by chance. Basically I ran a restore on the security settings of the affected machine by using the command secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose Which put right whatever was wrong. I was origenally trying to solve another problem, but it's also solved this one as well - bonus! Still have no idea what caused the problem in the first place, but at lease I can fix it now! Mike.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now