Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fokke Nauta Newsgroups: alt.comp.os.windows-11 Subject: Re: Can't connect to laptop Date: Wed, 14 May 2025 18:44:36 +0200 Lines: 42 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net Iq6yr47X9h2yJe7QX2SUjQzzlDQj0PE//7eoTjaBP0mZiMBCls Cancel-Lock: sha1:Av2wKQ9GvtDasAFKMVPZboTNuG8= sha256:gt/8ldUXhwTVbesUWR4eb64jBS53eGnnwVpSzET+BNk= User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: nl In-Reply-To: Xref: csiph.com alt.comp.os.windows-11:19246 On 12/05/2025 22:51, Paul wrote: > On Mon, 5/12/2025 2:59 PM, Fokke Nauta wrote: >> On 12/05/2025 15:29, Graham J wrote: >>> Fokke Nauta wrote: >>> [snip] >>>> The other W10 pc's have BitDefender Antivirus Plus. Perhaps I should uninstall Avira and install BitDefender? >>> >>> Worth a try. >>> >>> Uninstall Avira first, then see if folder sharing works.  If so, install Bitdefender and test again. >>> >> >> I'm going to do that. >> I'll come back with it. >> >> Fokke > > When dealing with any AV product, there are *two* steps. > > 1) Go to Programs and Features and remove the program. > Make sure you have recorded the license key for later usage. > Don't delete the program, without ascertaining you have records of the license value. > > 2) The second step involves a "Cleaner Application", which is > run as a separate step. Step (1) does not result in complete > removal. This is why step (2) is required. > > This article indicates that Avira recommends manual cleaning for Step (2). > Some companies provide an executable that removes the files, and that > file is an executable you would download. > > https://support.avira.com/hc/en-us/articles/360002858514-How-do-I-perform-a-manual-reinstallation-of-my-Avira-product?utm_medium=KB&utm_source=CS > > Paul > I uninstalled Avira. My shares were now accessible from the network. I installed BitDefender, and it was the same. My shares are still accessible from the network. So that problem was solved. Fokke