On uninstallation, there is an error because "LICENSE.txt" doesn't exist that prevents it from completing
See original GitHub issueWhen uninstalling the plugin, I got an error message that said the file C:\Users\MYUSER\AppData\Local\Microsoft\VisualStudio\16.0_1d542bea\Extensions\LICENSE.txt
doesn’t exist which prevents the plugin from uninstalling. Manually creating that file allowed me to uninstall it successfully.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
License file with no extension fails to pack with dotnet ...
If I remove the <PackageLicenseFile>license</PackageLicenseFile> line, it packs fine and license file is added to nupkg. It also works if I drop ...
Read more >How to troubleshoot Windows Installer errors
Describes how to troubleshoot problems that occur when you install, uninstall, or upgrade a program on a Windows-based computer by using Windows Installer....
Read more >Troubleshoot Creative Cloud package installation errors
Learn how to diagnose, troubleshoot, and resolve errors that occur while installing or uninstalling packaged Creative Cloud apps.
Read more >How do I uninstall a Windows service if the files do not exist ...
At method 1, you may experience "The specified service does not exist as an installed service" error, although you see the service at...
Read more >The License Manager is Not Functioning or is Improperly ...
Issue You saw an error message similar to the following when attempting to launch AutoCAD or F/X CAD: License Error: The License manager...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’ve just released a new version (
v11.0.0
) that fixes this issue. (#117)I encountered the same issue,thanks for @peeush-the-developer