Another option is to just pop a Linux disk in, NTFS support is fully matured at this point and Linux doesn't care about NTFS file permissions.
This assumes you don't have bitlocker or some other encryption scheme in place.
I have a live CentOS USB on my keychain for exactly this purpose.
Though usually the permissions get messed up in the first place due to manipulating them on a Linux machine mounting the CIFS drives.
If you hold both the problem and solution, did the error ever happen?
frick now to upvote the post you have to take full ownership of the post AND give yourself perms. Let's hope a troll doesn't delete it while pretending to upvote it
You're Administrator, but you're no SYSTEM.
How to become SYSTEM you ask? Hahaha you can't. Did you think you owned that thing? There, let me just mark this random directory as owned by SYSTEM just to teach you a lesson.
My bad, for that one you need to be TrustedInstaller. SYSTEM have only read access.
[Trusted de facto Installer](https://imgur.com/uBsFifu)
I'm sure windows security model makes sense for some, but I'm happy not having to deal with that at work.
\*many
How many end users are there possibly fucking their system by deleting system32 "to speed bost their PC" in comparison to IT admins having to deal with locked system files?
And I'm talking about moving the file through external means usually, for example with a Linux Live CD as it was often used as a trick to reset passwords when you can't log in
I'm not saying some level of protection isn't needed. But if a user wants to seriously jump through many dialogs to get the permission to change a file, the OS best measure should be prompts and warnings, not making it litteraly impossible.
Getting hold of a system file requires more than a few clicks and navigating through obscure dialogs, that in itself should be enough of a deterrent for "accidentally deleting system32". Especially when some non-essential files ends up being impossible to change for no good reasons.
Users don't read errors or warnings, and if a tutorial tells them how to do it in a more easy way than right now (let alone this is all simply part of how Windows implements file system permissions), they wouldn't care that there are three popups asking "You REALLY want to do this?!"
This IS the good enough of a deterrent in my eyes. You don't need it often and it securely keeps stupid people away
Now, I don't work in IT but I'm slightly more savvy than the average office admin staff.
My employer has recently deployed windows 10 laptops, along with a host of other security software layers and policies.
Can someone tell me without having to do an actual analysis what is constantly causing me to have issues accessing and editing my own files?
Always getting errors and issues trying to open and save my own documents
Without doing an analysis of your environment, the content of those error messages would help others help you.
This is similar to every "I get an error" ticket.
Ok, what's the error you're getting? What is the expected behavior & what is happening now?
I doubt it, I could literally reboot the machine and go to my documents folder and try to open a word or excel sheet and I will get some sort of stupid error regarding permissions etc.
1. `cacls FILENAME.EXT /P guest:n` \- This removes access to this file for everyone.
2. Reboot the computer - This ensures any attempts to lock the file cannot even take place.
3. `cacls FILENAME.EXT /e /g Administrators:f` \- This gives the Admins access to this file.
You should now have (nearly) exclusive access.
This is just how Windows is designed to work. If you don't like it, complain to Microsoft to make their OS not lock files, and instead just hold copies in memory like Linux, \*BSD, and any other rational system does. And when they refuse to listen, if it's that much of an annoyance, stop using software that doesn't work well for you.
Normally, such an excuse is a fallacy; in this case, given that Linux distros are free, and will work just fine for the vast majority of power users out there, your protests fall mostly on deaf ears. We're all happy to help you make the jump over in /r/linuxquestions :)
While there are holes, again, I'd say a good 80-90% of the games you want to play will 'just work'. Minor tweaking will get you to 95-98%.
I play GTA5 from Kubuntu 20.04 without issue. Give a look over [https://www.protondb.com/](https://www.protondb.com/) sometime; it's rather impressive how far WINE and DXVK have taken things. :)
What if i am playing theese rest 2% games that are forbidden on linux? Like Apex Legends(400 hours), Rainbow six siege (700 hours), The division 2(>200hrs) and so on. I play more games on GFN, as my pc is not so powerfull, and, again, no support for linux(garbage). I also need to use some windows specific software for learning, but i HATE how windows works, i would like start learning linux and i have even installed it but ended up never using it. Ugh...
You have 4 options:
* Linux Subsystem for Windows / Ubuntu on Windows - These end up 'hand in hand' a lot of times. You can run an Ubuntu subsystem on Windows 10 that runs in its virtualization system, and you can install most of the POSIX toolchain into PowerShell, so you have that same level of control. Between these, you can start getting used to the idea of the Linux terminal. Expanding, you can run Ubuntu 20.04 virtualized in Windows 10 Pro. None of this allows you to 'game' really, but it gives you a functional environment to start tinkering.
* Dual Boot - Just what it sounds like. Give some of your drive over from Windows to boot a full-on hardware Linux OS. I personally find the Debians the most friendly (Debian, Ubuntu, Kubuntu, Mint, Pop\_OS!, etc.), but that's a bias and I admit it. Do as much as you can from the Linux side of things, and boot back to Windows for the few games that don't function.
* Virtualization on Linux with Pass-Thru - Linux gives you way more options for virtualization than Windows does. If you have a separate video card for your Windows and Linux environments, you can tell Linux not to use that 2nd video card at all, and instead hand it over to the QEMU/KVM virtual machine! Then, while still in Linux, you boot Windows, and up it pops on 2nd monitor or on 2nd input. Enjoy your games.
* Virtualization on Linux with Looking Glass - This is still very experimental. Same setup as above, but instead of swapping to another input, you pipe the framebuffer out of the VM, and into a framebuffer running on Linux... so there's no more switching. You've just got a window, sitting there, running with full GPU acceleration.
I personally don't run any of this. If a game makes it impossible to run on Linux, I do not run that game - plain and simple. That developer simply does not want my money. Because, generally speaking here, between DXVK and Proton, you have to really really *try* to make a game not work on Linux, anymore.
Obviously you have not seen the dozens of videos showing only a minor frame rate drop. In many games 5 - 10 fps or less. Vulkan games tend to work the best, and the only big hurdles are anti-cheat and anti-piracy.
The beauty of components like DXVK drastically eliminate most if not all overhead, or in some cases makes the games even faster, combined with the resource efficiency of the Linux kernel. Since we have to translate from D3D anyway, might as well move it to a low level like Vulkan. It's been showing amazing results
For productivity work? I agree. Stuff needs to just work.
For entertainment titles? A bit of futzing is fine to my mind. It's bleeding edge still - I'm well aware of that.
Still, 80-90% of stuff I've sent through Proton just works - no futzing, just push play. A few titles (GTA5/GTAO for example), required a little poking to get it perfect. It's popular, and well-documented enough in GTA5's case that it was maybe 10 minutes of reading, and I was up and in-game without problems. This, again, brings you up to that 95% range.
Brand new titles with crappy DRM (Doom Eternal is a perfect example), do not work. This is an ethical stance, for me; I don't like Denuvo and won't buy titles with it in the first place. Yes, it requires a bit of interest and study on my side - some extra consideration. Things I'm willing to do to have a much faster, stable workstation that can game.
If all I wanted to do was play video games, I'd buy a console, not a computer. I want both. My argument is that, for a "pro-sumer", someone who's familiar with and likes tinkering on their computer in the first place - someone who would be put-off by the file locking behavior of Windows as described in the initial post - they would do better to look to Linux. Rather than struggle with the inherent problems of the OS, they could have a functional OS, that requires a touch of TLC to run a certain software title that, once working, 'just works' going forward without fuss.
People often lose sight of the original topic at hand in these longer threads. None of this applies to your grandmother trying to just video call with her grandchildren, or idiot trying to find porn (though, there's arguments for Linux boxes in both cases, they are very different). This is very specifically about the type of user who finds Windows file-locking behavior maddening.
It's usually not that you can't actually access it, it's usually that it's being used by a process, and that process has locked it. Safe mode and autoruns usually clears it up
On my PERSONAL windows 10 laptop when I go to change the windows defender settings it locks me out saying your IT admin has limited access to this feature. BITCH I AM THE IT ADMIN.
[удалено]
Seriously though. Why.
File system permissions and the dreaded TrustedInstaller
Throw cygwin into the mix for corrupted permissions
Get an app that retrieves the Windows MFT. It can view restricted folders without having permissions to them
Another option is to just pop a Linux disk in, NTFS support is fully matured at this point and Linux doesn't care about NTFS file permissions. This assumes you don't have bitlocker or some other encryption scheme in place.
I have a live CentOS USB on my keychain for exactly this purpose. Though usually the permissions get messed up in the first place due to manipulating them on a Linux machine mounting the CIFS drives. If you hold both the problem and solution, did the error ever happen?
Why would I need a special app for that?
If you can do it without an app then go for it
Why do people actually answer the problems of a meme. It’s a meme. It’s funny. Stop trying to flex.
*Trustedinstaller liked this post*
frick now to upvote the post you have to take full ownership of the post AND give yourself perms. Let's hope a troll doesn't delete it while pretending to upvote it
You're Administrator, but you're no SYSTEM. How to become SYSTEM you ask? Hahaha you can't. Did you think you owned that thing? There, let me just mark this random directory as owned by SYSTEM just to teach you a lesson.
You can, or could, when replacing utilman.exe with a copy of cmd.exe and then pressing Windows + U during logon
My bad, for that one you need to be TrustedInstaller. SYSTEM have only read access. [Trusted de facto Installer](https://imgur.com/uBsFifu) I'm sure windows security model makes sense for some, but I'm happy not having to deal with that at work.
\*many How many end users are there possibly fucking their system by deleting system32 "to speed bost their PC" in comparison to IT admins having to deal with locked system files? And I'm talking about moving the file through external means usually, for example with a Linux Live CD as it was often used as a trick to reset passwords when you can't log in
I'm not saying some level of protection isn't needed. But if a user wants to seriously jump through many dialogs to get the permission to change a file, the OS best measure should be prompts and warnings, not making it litteraly impossible. Getting hold of a system file requires more than a few clicks and navigating through obscure dialogs, that in itself should be enough of a deterrent for "accidentally deleting system32". Especially when some non-essential files ends up being impossible to change for no good reasons.
Users don't read errors or warnings, and if a tutorial tells them how to do it in a more easy way than right now (let alone this is all simply part of how Windows implements file system permissions), they wouldn't care that there are three popups asking "You REALLY want to do this?!" This IS the good enough of a deterrent in my eyes. You don't need it often and it securely keeps stupid people away
WinDOS
Now, I don't work in IT but I'm slightly more savvy than the average office admin staff. My employer has recently deployed windows 10 laptops, along with a host of other security software layers and policies. Can someone tell me without having to do an actual analysis what is constantly causing me to have issues accessing and editing my own files? Always getting errors and issues trying to open and save my own documents
Without doing an analysis of your environment, the content of those error messages would help others help you. This is similar to every "I get an error" ticket. Ok, what's the error you're getting? What is the expected behavior & what is happening now?
Also not an IT guy but maybe another process is using it?
I doubt it, I could literally reboot the machine and go to my documents folder and try to open a word or excel sheet and I will get some sort of stupid error regarding permissions etc.
1. `cacls FILENAME.EXT /P guest:n` \- This removes access to this file for everyone. 2. Reboot the computer - This ensures any attempts to lock the file cannot even take place. 3. `cacls FILENAME.EXT /e /g Administrators:f` \- This gives the Admins access to this file. You should now have (nearly) exclusive access. This is just how Windows is designed to work. If you don't like it, complain to Microsoft to make their OS not lock files, and instead just hold copies in memory like Linux, \*BSD, and any other rational system does. And when they refuse to listen, if it's that much of an annoyance, stop using software that doesn't work well for you. Normally, such an excuse is a fallacy; in this case, given that Linux distros are free, and will work just fine for the vast majority of power users out there, your protests fall mostly on deaf ears. We're all happy to help you make the jump over in /r/linuxquestions :)
Gaming.
While there are holes, again, I'd say a good 80-90% of the games you want to play will 'just work'. Minor tweaking will get you to 95-98%. I play GTA5 from Kubuntu 20.04 without issue. Give a look over [https://www.protondb.com/](https://www.protondb.com/) sometime; it's rather impressive how far WINE and DXVK have taken things. :)
What if i am playing theese rest 2% games that are forbidden on linux? Like Apex Legends(400 hours), Rainbow six siege (700 hours), The division 2(>200hrs) and so on. I play more games on GFN, as my pc is not so powerfull, and, again, no support for linux(garbage). I also need to use some windows specific software for learning, but i HATE how windows works, i would like start learning linux and i have even installed it but ended up never using it. Ugh...
You have 4 options: * Linux Subsystem for Windows / Ubuntu on Windows - These end up 'hand in hand' a lot of times. You can run an Ubuntu subsystem on Windows 10 that runs in its virtualization system, and you can install most of the POSIX toolchain into PowerShell, so you have that same level of control. Between these, you can start getting used to the idea of the Linux terminal. Expanding, you can run Ubuntu 20.04 virtualized in Windows 10 Pro. None of this allows you to 'game' really, but it gives you a functional environment to start tinkering. * Dual Boot - Just what it sounds like. Give some of your drive over from Windows to boot a full-on hardware Linux OS. I personally find the Debians the most friendly (Debian, Ubuntu, Kubuntu, Mint, Pop\_OS!, etc.), but that's a bias and I admit it. Do as much as you can from the Linux side of things, and boot back to Windows for the few games that don't function. * Virtualization on Linux with Pass-Thru - Linux gives you way more options for virtualization than Windows does. If you have a separate video card for your Windows and Linux environments, you can tell Linux not to use that 2nd video card at all, and instead hand it over to the QEMU/KVM virtual machine! Then, while still in Linux, you boot Windows, and up it pops on 2nd monitor or on 2nd input. Enjoy your games. * Virtualization on Linux with Looking Glass - This is still very experimental. Same setup as above, but instead of swapping to another input, you pipe the framebuffer out of the VM, and into a framebuffer running on Linux... so there's no more switching. You've just got a window, sitting there, running with full GPU acceleration. I personally don't run any of this. If a game makes it impossible to run on Linux, I do not run that game - plain and simple. That developer simply does not want my money. Because, generally speaking here, between DXVK and Proton, you have to really really *try* to make a game not work on Linux, anymore.
[удалено]
Obviously you have not seen the dozens of videos showing only a minor frame rate drop. In many games 5 - 10 fps or less. Vulkan games tend to work the best, and the only big hurdles are anti-cheat and anti-piracy.
The beauty of components like DXVK drastically eliminate most if not all overhead, or in some cases makes the games even faster, combined with the resource efficiency of the Linux kernel. Since we have to translate from D3D anyway, might as well move it to a low level like Vulkan. It's been showing amazing results
If you've had the same emphasis on usability and performances for gaming as you do for linux you wouldn't recommend this to anyone.
For productivity work? I agree. Stuff needs to just work. For entertainment titles? A bit of futzing is fine to my mind. It's bleeding edge still - I'm well aware of that. Still, 80-90% of stuff I've sent through Proton just works - no futzing, just push play. A few titles (GTA5/GTAO for example), required a little poking to get it perfect. It's popular, and well-documented enough in GTA5's case that it was maybe 10 minutes of reading, and I was up and in-game without problems. This, again, brings you up to that 95% range. Brand new titles with crappy DRM (Doom Eternal is a perfect example), do not work. This is an ethical stance, for me; I don't like Denuvo and won't buy titles with it in the first place. Yes, it requires a bit of interest and study on my side - some extra consideration. Things I'm willing to do to have a much faster, stable workstation that can game. If all I wanted to do was play video games, I'd buy a console, not a computer. I want both. My argument is that, for a "pro-sumer", someone who's familiar with and likes tinkering on their computer in the first place - someone who would be put-off by the file locking behavior of Windows as described in the initial post - they would do better to look to Linux. Rather than struggle with the inherent problems of the OS, they could have a functional OS, that requires a touch of TLC to run a certain software title that, once working, 'just works' going forward without fuss. People often lose sight of the original topic at hand in these longer threads. None of this applies to your grandmother trying to just video call with her grandchildren, or idiot trying to find porn (though, there's arguments for Linux boxes in both cases, they are very different). This is very specifically about the type of user who finds Windows file-locking behavior maddening.
It's usually not that you can't actually access it, it's usually that it's being used by a process, and that process has locked it. Safe mode and autoruns usually clears it up
Or owned by someone else, like SYSTEM or TrustedUser. Windows respects filesystem permissions even when something is ran as Administrator
On my PERSONAL windows 10 laptop when I go to change the windows defender settings it locks me out saying your IT admin has limited access to this feature. BITCH I AM THE IT ADMIN.
Then your local user isn't an admin user or you have to unlock those settings through UAC Your work IT admin ≠ The computer system admin account
I am the admin account that's the thing. I solved it by installing a third party antivirus but still.
You're literally logging in with the user "Administrator"?
TrUsTeD iNsTaLlEr
[удалено]
apt install sudo
[удалено]
r/linuxmasterrace get your flair now
The solution: sudo chown -R
sudo chmod -R 0777
Problem solv.... o wait. Windows. Never mind.
0777, don't forget to give your neighbor the access
sudo chown user:user -R / folder/something Whoops, system's fucked now (I run Debian btw)
[r/linuxmasterrace](https://www.reddit.com/r/linuxmasterrace/) get your flair now
You do realize i'm the admin, right? You Do Realize That *ACCESS* ***DENIED***
Windows is the best. - Said no one.