From: Steinar Bang <sb@dod.no>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Tue, 04 Aug 2020 14:01:14 +0200 [thread overview]
Message-ID: <upzc8seuvcvp.fsf@dod.no> (raw)
In-Reply-To: <f4e8541c-de04-e250-f3f7-22ac83540c87@cs.umass.edu>
>>>>> 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.
next prev parent reply other threads:[~2020-08-04 12:02 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 [this message]
2020-08-04 13:12 ` Hamish McIntyre-Bhatty
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=upzc8seuvcvp.fsf@dod.no \
--to=sb@dod.no \
--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).