Tweaking.com Support Forums
Main Forum => Tweaking.com Support & Help => Topic started by: FirstAidPoetry on January 18, 2017, 05:44:42 pm
-
Skipping Repair.
Repair is for Windows v6 (Windows Vista & Newer) or higher.
Current version: 10.0.14393.693
That...sounds wrong, am I missing something? Pretty sure Windows 10 is newer that Vista ;).
-
what repair is skipping?
can you upload the repair log?
-
I ran the Reset File Permissions (02), nothing else.
System is Win 10 x64 Home.
Log attached.
-
give me a moment i got a windows 10 machine up and running im going to run and compare ill see what the program is doing.
-
hmmm I can't recreate this effect I sent Shane an email with a copy of your log. I'm waiting for a reply so in the meantime lets get some info:
First things first is did you run these repairs in safe mode with networking?
-
They were run in normal mode, but I absolutely do not mind trying the same process in safe mode both with and without networking, if that helps?
-
the reason being is 3rd party software can stop the repairs from running. :wink: safe mode the 3rd party software cant stop them. :cheesy:
-
Quite understandable, but it should still not fail a OS version check, which is more or less what the error implies.
Speaking of implied things, I'll take down the server and try running the same operation in safe mode as soon as there's less client load on it. (it's a media server) and see if it makes any difference.
-
you are running on a server? the repairs are not tested or designed to run on servers.
can you open cmd and type this in for me so i can see what it is saying.
wmic OS get Caption,CSDVersion,OSArchitecture,Version
-
It's just a server, not a server OS by any means. Just regular Windows 10 x64 Home running an FTP and a media server. Meaning, if I reboot now I will hear shouting for cutting of my girlfriend's streaming of our Futurama DVDs :)
Microsoft Windows 10 Home 64-bit 10.0.14393
-
okay hmmmm alright for now im going to wait for a reply from Shane see what he says. :artist: i'm stumped at the moment and it could be something in the code which only shane has access to lol could be calling windows 10 home wrong.
-
Shane responded back it looks like a minor bug and it looks like your repair still succeeded because it did take 6 minutes.
Shane will fix that bug in the next version. Thanks for posting about it and helping out :smiley: