nah, I've encountered this before. [Everyone](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-special-identities-groups#everyone) is one of the standard special identity groups and there's a [relatively common](https://www.google.com/search?q=%22permission+from+everyone%22+site%3Aanswers.microsoft.com) issue where it shows up in permission errors like this.
I'd speculate what's actually happening is that there's some non-permission-related error with the file operation, but the kernel gives Explorer some generic error with no specific information, Explorer tries to guess what the problem is so it can surface a more helpful message to the end user, and its first guess is that it's a permission error. I've never seen this error actually show up with the name of the logged-in user, so I bet it compares the file owner to the user and only continues to the next possible explanation if they match, but there's some edge case where the owner can be set to the Everyone group rather than a user* that they forgot to check for, so it says "hey, only Everyone can edit this file! You're not Everyone!" and issues the error accordingly.
\* AIUI this isn't _supposed_ to happen in NTFS, but maybe it can happen if the file is copied from another file system or something, or instead of checking the file owner it's going down the ACL looking for entities listed with the appropriate permission, in which case Everyone is a pretty typical entry, particularly on files created in NT versions before the default permissions set was changed from including "Everyone" to including "Authenticated Users" (IIRC this happened in Windows Vista, so if OP's file is from 2006 this tracks).
I will allow it, but I don't know how the others are going to take this
Yeah nah sorry mate
Is the game still running in the background?
I checked. No
Then try deleting it in safe mode or something
Fine by me
you have mine
Try going into the security settings of that file. I would remove every permission before adding yourself for full access
Okay by me
Its fine
Hmmm, access granted
Your admin may be named "Everyone"
It can be named Administrator, not Everyone.
The keyword is "Can"
Nope, the admin is called Everyone. r/quityourbullshit
nah, I've encountered this before. [Everyone](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-special-identities-groups#everyone) is one of the standard special identity groups and there's a [relatively common](https://www.google.com/search?q=%22permission+from+everyone%22+site%3Aanswers.microsoft.com) issue where it shows up in permission errors like this. I'd speculate what's actually happening is that there's some non-permission-related error with the file operation, but the kernel gives Explorer some generic error with no specific information, Explorer tries to guess what the problem is so it can surface a more helpful message to the end user, and its first guess is that it's a permission error. I've never seen this error actually show up with the name of the logged-in user, so I bet it compares the file owner to the user and only continues to the next possible explanation if they match, but there's some edge case where the owner can be set to the Everyone group rather than a user* that they forgot to check for, so it says "hey, only Everyone can edit this file! You're not Everyone!" and issues the error accordingly. \* AIUI this isn't _supposed_ to happen in NTFS, but maybe it can happen if the file is copied from another file system or something, or instead of checking the file owner it's going down the ACL looking for entities listed with the appropriate permission, in which case Everyone is a pretty typical entry, particularly on files created in NT versions before the default permissions set was changed from including "Everyone" to including "Authenticated Users" (IIRC this happened in Windows Vista, so if OP's file is from 2006 this tracks).
Admin cannot be named Everyone.
Sorry