From: Brent Epp <brent@pdc.ca>
To: cygwin@cygwin.com
Subject: Re: Permissions issues after installing Windows 10
Date: Fri, 3 Jun 2022 07:23:05 -0500 [thread overview]
Message-ID: <75c20491-164b-b3cb-55d0-a482240842c3@pdc.ca> (raw)
In-Reply-To: <CANV9t=S0LmwOtmh_PhaX3wAMKEKmq-u+9HPZ3a3KkPv3AvU_BQ@mail.gmail.com>
On 2022-06-02 10:14, Bill Stewart wrote:
> On Thu, Jun 2, 2022 at 6:44 AM Brent Epp wrote:
>
> In the [Security] tab for these files or directories, under "Group or
>> user names", it lists the owner as "Account Unknown(S-...)". In some
>> cases, these files are completely inaccessible and I can't even take
>> ownership or change the permissions. I have to either restore them from
>> a backup or boot to a Linux environment to access them.
>>
> Windows displays "Account Unknown" (with a SID) in the ACL when it can't
> resolve the SID reference.
>
> There can be a number of reasons for this. One common reason is that the
> SID belongs to a domain account and the domain is not accessible. Another
> is that the SID belongs to a local account on a different computer (e.g., a
> removable disk is moved between computers and local accounts are in the
> ACL).
This is essentially what happened (removable disk moved from one
computer to another).
> Well-known SIDs (e.g., S-1-5-32-544 for the local Administrators
> group, etc.) should resolve from any computer.
I would think so too, but that doesn't appear to be happening.If it
makes a difference, the SID actually starts with S-1-5-21. I have to
manually take ownership in order to even access the files at all.
- Brent
next prev parent reply other threads:[~2022-06-03 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 15:00 Brent Epp
2022-05-08 15:35 ` Andrey Repin
2022-06-02 12:43 ` Brent Epp
2022-06-02 15:14 ` Bill Stewart
2022-06-03 12:23 ` Brent Epp [this message]
2022-06-03 12:47 ` Achim Gratz
2022-06-03 16:42 ` Bill Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75c20491-164b-b3cb-55d0-a482240842c3@pdc.ca \
--to=brent@pdc.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).