windows10, I've uninstalled simpleDNScrypt because it causes some problems with steam, but some files are still not completely uninstalled and now the proxies are stuck to my computer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- desktop, networking
Research direction
Start by reproducing the Windows 10 uninstall flow and inspect the remaining simplednscrypt.exe, uninstall.exe, and dnscrypt-proxy.exe files alongside the proxy settings described in the report. Done means uninstalling SimpleDNSCrypt no longer leaves proxy values that are automatically restored and online connectivity works normally.
Written by the indexing model from the issue text.
Description
I'm sorry if this is a stupid question, it's my first time here and I only have basic knowledge about internet
So when I uninstalled SimpleDNScrypt on settings, it says it has been uninstalled but when I check my drive where dnscrypt are downloaded, there's still some files left for ex : simplednscrypt.exe, uninstall.exe, bunch of words and numbers,dnscrypt-proxy.exe. three of the .exe didn't work when I click on it. I just delete all the files and empty recycle bin, but now I have this problem which is when I go to proxy settings, I saw this, the numbers and *.local are autofilled and when I delete and open the settings again, it autofills again. It causes my online games to never connect. I think that I didn't uninstalled simplednscrypt completely, if so then how can I uninstalled it completely? I don't have the files anymore since it's been deleted but the proxies are still there. When I go to safemode with networking, the proxy settings are no longer there, no longer greyed out, no longer refilled and everything came back to normal.
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DNSCrypt/SimpleDnsCrypt
-
Website problem Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
DNSCrypt/SimpleDnsCrypt#586 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DNSCrypt/SimpleDnsCrypt#585 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
DNSCrypt/SimpleDnsCrypt#584 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
DNSCrypt/SimpleDnsCrypt#582 · 6 comments ·
-
New release? Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
DNSCrypt/SimpleDnsCrypt#581 · 10 comments ·
All issues in DNSCrypt/SimpleDnsCrypt
Similar issues
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
dependencies needs-team-triage server-Azure.Mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
aspnet-core/svc aspnetcore-signalr/subsvc doc-enhancement Pri2 SignalR
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/AspNetCore.Docs#37729 ·