X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 734BF3858034 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1639408074; bh=FHc29OJ+vJLkPy09629yTTYHwKZVKMS583U2IKj1nqY=; h=Date:From:To:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Reply-To:From; b=R8bqNBQTtcbibzxz1cuA6fVH9MMssg3RV1mp7cOKlAuKPuMO28S7dbxYDGBLi0pKB R/jUZEyvsmkHKasCu1WcQ0LfDKQKn1yYaVacypOu+wEP5xem0B2BlImuHUfdi/GBrk PhY+9tf2OwhHEmREE81FfY5P5aB+PrwbXihqOLhg= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C2BBF3857817 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=cygwin.com Date: Mon, 13 Dec 2021 16:06:24 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <015801d7f00f$b117ed70$1347c850$@dyalog.com> <20211213200623 DOT 606ba51691c1209a2f2c2a75 AT nifty DOT ne DOT jp> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20211213200623.606ba51691c1209a2f2c2a75@nifty.ne.jp> X-Provags-ID: V03:K1:Aj0UfOn+T/830Ved/VjD5ppx1SHJtDfu402z14hwm1tW3HJB97D UkxWJVQ2fOSlA62s53Ww/zpDKrwDyq0aIvFIWLFkfNuLIssi5gz75SCEDyXcjnkBkaAGx2Q kB8QuYUTusZLTbtw/Wk8SacniKPEA/cxNMIef7TaxoystaeZWgWP4rk8k2u19kCsLoorhrX K8qhLXzpGbnDrP8g5aVAQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:YjRG40oe0JA=:TSfKKNySnML5firlb5Bltp XYIW+YCPTNWTw07+KOaNAIIl1EV+bkwI+1UqLXdfRFWzgJ3cl4JXFMSv/rbN4zzFiqFAkDYha KKJF3W8NNdJ/setPs3UqKiwBIm2xVwaRAz+uBFSCubdvD9I0QPMwPUJ2mh+/jzqfzt/HzMGP9 0uivVO9WGQOq4+W2jNmCyR8eyj5WjM3Br0hlmd25Rfjjj4ukLfconUizB4DPtHpIq/jV1hwJ6 gQkYyKtWjikNWYpi77x0LfJAXfYV5A6Ov89fyA19UiMSDYwQvAltCsy3OqZ6bQMsQYj/EBC5m A3wIlccf4gYAmlIVxXMHCsfwL8CLANX3muvE78Pic/u6K87EApcgi7NeJT6yHgRE4h/5uamKe g6XVLzuT8ZNSVZ7R14qPHree51bpLQ0kSIIU/+Uw+5XNiDwCNRYugLQH7UDxJIjv9SVl3dIzU TvpBq/hzwePsqmxiVM4n307qSKHRt5sx2Ul5rswU+PjFGF0LdgEN+hnvoZ8CtcKk0tI5cE3a7 0P8BcXdH+O/7SQJPoB82GV62rEG5bCyG/w5kj7QGJ9ee/rIejism8Iv6MyxZxk5voHmcJvICs yWEHWPnDoyk1vt89cqyPr39iqOOn81t+MBWcUA13xwuYeduKFJTKl8f6YfQZejL0wRtNsmk5/ H8OCM5kuibQKK9El+jkY3ugT6lftBSx+h6MP2Vg1/geSxnHPUoECOJPD/rcEnefiwbb8UrDYS joYEcNbsS9lDAgHf X-Spam-Status: No, score=-99.1 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, JMQ_SPF_NEUTRAL, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Dec 13 20:06, Takashi Yano wrote: > On Mon, 13 Dec 2021 10:53:41 -0000 > "john daintree" wrote: > > I've just upgraded a machine from Windows 10 to Windows 11. Part of my work > > process is now broken because when starting cmd from Cygwin with the current > > directory on a mounted drive I get the following error/warning/issue: > > > > > > > > > > > > /cygdrive/j$ cmd > > > > '\\nas00.\devt\users\johnd' > > > > CMD.EXE was started with the above path as the current directory. > > > > UNC paths are not supported. Defaulting to Windows directory. > > > > Microsoft Windows [Version 10.0.22000.348] > > > > (c) Microsoft Corporation. All rights reserved. > > > > > > > > C:\Windows> > > > > > > > > > > > > The drive J: is mounted as something on our network (I've redacted a bit of > > the path, for probably no good reason) > > > > > > > > Is there a workaround? Or is this something that can be fixed in Cygwin? > > Thanks for the report. This was already fixed recently in git head. > > https://cygwin.com/pipermail/cygwin/2021-December/250153.html > https://cygwin.com/pipermail/cygwin-patches/2021q4/011583.html > > Please wait for the next cygwin release or new developers snapshot. New developer snapshot is available on https://cygwin.com/snapshots/ Corinna -- 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