X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A344F3856273 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pdc.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pdc.ca X-Zone-Loop: 2ca140085b8759fe6171185a8394a5625b5777993935 X-Originating-IP: [140.82.40.27] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=pdc.ca; s=x ; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=n/HV699ehGd4nRq4ov9kSmvd+XrGzFbf03W8g2ljgkY=; b=GhNR7AvTiicxbZs9Sy/9u7CJwG Lb+BUrV0JsxJtogi2bBHBOYvDOxPEDYyRQsmLZlldMDvi4Ap4LzLaxlSS83FRzsb6nga9N+lGCyqV yBFnCd18S79TW1x4gGAJHuEP7r+93n8f+bwg4oyr9g02w+AZwJQQMs4QZ/cDWreyCAGIByHMYlG2l NCJoMRFmXc9/NLtcLbubKw90Is/4avQO3Y5Ge2bNYjMzWRcvVjJqOiW7SAJlWJRQNw3SbMCETKvIY TVbPR+XgleXM/cTH3uGji63N9EqhcKYp47pYnwA5u/advaRqDJk3T2w7BJLgRfhR9LSKRmss89eu9 vqJGPoWg==; Subject: Re: Permissions issues after installing Windows 10 To: cygwin AT cygwin DOT com References: <26dc3119-0f36-1331-1403-9e994a697d89 AT pdc DOT ca> <1351760318 DOT 20220508183530 AT yandex DOT ru> <65f61260-7a7f-e7dc-e3f6-4eddead9da74 AT pdc DOT ca> From: Brent Epp X-Tagtoolbar-Keys: D20220603072305466 Message-ID: <75c20491-164b-b3cb-55d0-a482240842c3@pdc.ca> Date: Fri, 3 Jun 2022 07:23:05 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-AuthUser: brent AT pdc DOT ca X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00, DKIM_INVALID, DKIM_SIGNED, KAM_DMARC_STATUS, KAM_NUMSUBJECT, NICE_REPLY_A, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 253CNvM0004263 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple