public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Tue, 4 Aug 2020 14:12:49 +0100	[thread overview]
Message-ID: <DB7PR02MB3996FDCF4468C5918E057AEAE74A0@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <upzc8seuvcvp.fsf@dod.no>


[-- Attachment #1.1.1: Type: text/plain, Size: 1629 bytes --]

On 04/08/2020 13:01, Steinar Bang wrote:
>>>>>> Eliot Moss <moss@cs.umass.edu>:
>> On 8/2/2020 4:25 PM, Steinar Bang wrote:
>>>>>>>> "Holger, Vodafone" <holger.dietze@vodafone.de>:
>>>> And I have checked on my system today, my strace output stop at the same tmmon64.dll, so it is likely the reason for the error.
>>>> I have opened a service request with our IT and wait for their answer.
>>> Did you get any further with this?
>>>
>>> I added the directory C:\cygwin64\bin to the Trend Micro exclusion list,
>>> but that didn't help: XWin.exe still won't start.
>>>
>>> Is it neccessary to do some kind of cache flushing? If so: how?
>> I wonder it you might need to add directories containing the .dll files
>> being loaded by your cygwin programs, too ...
> I googled up this documentation which states "All subdirectories in the
> directory path you specify will also be excluded."
>  https://docs.trendmicro.com/all/smb/wfbs-services/server/wfbs-svc/v3.7/en/docs/WebHelp/_WFBS-SVC/C08-Scans/ExcludingFilesFoldersFromScans.htm
>
> I changed the exclusion to be C:\cygwin64
>
> But I still have no luck in starting XWin.exe, unfortunately.
>
> --
> 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

In case this is any use, I updated a Windows 10 VM to 2004 to do a quick
test, and X11 worked okay for me. Having said that, I don't remember
what build you're on, but I'll happily try another build if needed.

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-08-04 13:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:57 Steinar Bang
2020-06-13  6:30 ` Marco Atzeri
2020-06-13  9:30   ` Steinar Bang
2020-06-13 11:22     ` Marco Atzeri
2020-06-13 12:00       ` Steinar Bang
2020-06-13 13:22         ` Marco Atzeri
2020-06-13 15:48           ` Steinar Bang
2020-06-13 16:44             ` Steinar Bang
2020-06-13 20:37       ` Andrey Repin
2020-06-13  9:35   ` Steinar Bang
2020-06-13  9:55     ` Steinar Bang
2020-06-13 11:31       ` Marco Atzeri
2020-06-13 12:03         ` Steinar Bang
2020-06-13 12:09           ` Steinar Bang
2020-06-13 13:14         ` Holger, Vodafone
2020-06-13 13:29           ` Marco Atzeri
2020-06-13  9:04 ` Steinar Bang
2020-06-13 21:15   ` Jon Turney
2020-06-14 10:44     ` Steinar Bang
2020-06-14 11:18       ` Henry S. Thompson
2020-06-14 16:12         ` Steinar Bang
2020-06-14 17:49           ` Marco Atzeri
2020-06-14 21:45             ` Steinar Bang
2020-06-14 22:21               ` Holger, Vodafone
2020-06-15 12:17                 ` Holger, Vodafone
2020-06-15 12:57                   ` Holger, Vodafone
2020-06-16  4:22                   ` Brian Inglis
2020-08-02 20:25                   ` Steinar Bang
2020-08-02 21:00                     ` Eliot Moss
2020-08-04 12:01                       ` Steinar Bang
2020-08-04 13:12                         ` Hamish McIntyre-Bhatty [this message]
2020-08-04 16:55                         ` ASSI
2020-06-16  4:59                 ` ASSI
2020-07-02 15:01               ` Steinar Bang
2020-07-02 22:12                 ` Holger, Vodafone
2020-06-16 11:46     ` Holger, Vodafone
2020-06-26  9:15       ` Holger, Vodafone
2020-07-02 14:42         ` Steinar Bang
2020-06-14  6:18 ` Marco Atzeri
2020-06-14 10:38   ` Steinar Bang

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=DB7PR02MB3996FDCF4468C5918E057AEAE74A0@DB7PR02MB3996.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --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).