Issue with permissions on surface pro 3 with Windows 10 build 10162
Hello
I have experienced a strange issue when updating my SP3 to build 10162. Suddenly I had lost all permissions to write on any of my folders, Onedrive would not sync anymore for example as it was unable to write.
I did tweak the permissions on the C drive with full control for everyone but it would not fix the problem. I also try to change the ownership, it did no fix the issue. Finally I used the fix_ownership registry tweak, it crashed my computer for good... So now I am back to 8.1 and obviously I have no issue since it is a brand new install.
While I can probably survive 8.1 until end of July I am concerned the same thing will happen when the official W10 is updated. I have used Windows 10 over the past few months on a Dell laptop with no issue of this kind. So I guess it is specific to SP3 (which I just got few days ago) , I was having issues installing the May firmware update for the SP3 so maybe that is the reason but I can't be sure.
Has anyone encountered the same issue with W10? Thanks in advance for your help
Sidenote: Both W10 and SP3 are amazing!
Igor
Hello
I have experienced a strange issue when updating my SP3 to build 10162. Suddenly I had lost all permissions to write on any of my folders, Onedrive would not sync anymore for example as it was unable to write.
I did tweak the permissions on the C drive with full control for everyone but it would not fix the problem. I also try to change the ownership, it did no fix the issue. Finally I used the fix_ownership registry tweak, it crashed my computer for good... So now I am back to 8.1 and obviously I have no issue since it is a brand new install.
While I can probably survive 8.1 until end of July I am concerned the same thing will happen when the official W10 is updated. I have used Windows 10 over the past few months on a Dell laptop with no issue of this kind. So I guess it is specific to SP3 (which I just got few days ago) , I was having issues installing the May firmware update for the SP3 so maybe that is the reason but I can't be sure.
Has anyone encountered the same issue with W10? Thanks in advance for your help

Sidenote: Both W10 and SP3 are amazing!
Igor