6/13/2023 0 Comments Mudlet unoffical squaresoft![]() ![]() Then this morning just now I uninstalled MS Teams (both instances, the one with Mudlet icon and one with real icon), and I restored the nupkg files from the Recycle Bin, ran MS Teams installer again, and now it's back to doing the Microsoft\Mudlet thing. Last night I deleted the nupkg files and ran the MS Teams installer, it went fine this time. 15:01:04> Program: Install path C:\Users\Atari\AppData\Local\Microsoft\Mudlet already exists, burning it to the ground 15:01:04> Program: About to install to: C:\Users\Atari\AppData\Local\Microsoft\Mudlet ![]() 15:01:04> UpdateManager: using rootAppDirectory: C:\Users\Atari\AppData\Local\Microsoft\Mudlet 15:01:04> Program: File does not contain contextual info: MSTeamsSetup_c_l_.exe 15:00:58> Program: RELEASES doesn't exist, creating it at C:\Users\Atari\AppData\Local\SquirrelTemp\RELEASES 15:00:58> Program: Starting install, writing to C:\Users\Atari\AppData\Local\SquirrelTemp 15:00:58> Program: Config already exists. 15:00:57> Program: Starting Squirrel Updater: -install. Not sure if future updates to Mudlet will be affected or no. SquirrelTemp was rebuilt immediately to be done up for MS Teams instead, and the program ran as needed. They could not find Mudlet's root install and were thinking maybe uninstalling Mudlet could help the issue?ĭeleting the folder %USERPROFILE%\AppData\Local\SquirrelTemp solved the problem! There is now a folder "AppData/Local/Microsoft/Mudlet" with "app" with Mudlet's icon, and "update" with Teams' icon, etc.ĭeleting this folder and trying to launch any installer for Teams just revives the folder. In Applications listed on Windows, "Microsoft Teams" is listed with Mudlet's icon and has an e-signature as being made by Mudlet Makers. When they installed MS Teams, it launched Mudlet instead. ![]() Today a player in Discord mentioned they did not use Mudlet in years, forgot they even have it installed. The workaround seems to be sorting the update.exe executable in folder %USERPROFILE%\AppData\Local\SquirrelTemp - or simply deleting the whole folder as is. It's a library for C# projects, so not for us GitHub - Squirrel/Squirrel.Windows: An installation and update fram. ( )Īn installation and update framework for Windows desktop apps - GitHub - Squirrel/Squirrel.Windows: An installation and update framework for Windows desktop apps Squirrel uses NuGet packages to create installation and update packages, which means that you probably already know most of what you need to create an installer. Squirrel is both a set of tools and a library, to completely manage both installation and updating your Desktop Windows application, written in either C# or any other language (i.e., Squirrel can manage native C applications). Squirrel is a library no? So either MS or Mudlet installer confuse something or leave confusing data behind or can play the blame game nowīut it does use some artifacts produced by nuget So it would be squirrel confusing something Both use Squirrel, the same installation framework: Concurrent Squirrel installations results in unpredictable behaviour Squirrel/Squirrel.Windows#1582Īdditional relevant advice by
0 Comments
Leave a Reply. |