-
|
Moved here from ungoogled-software/ungoogled-chromium-windows#474 as it's a local issue on my device, and not a general issue with ungoogled-chromium-windows. I'm running version 137.0.7151.103 of ungoogled-chromium-windows 64 bit. I've previously been able to update just by downloading the installer exe, run it, allow the application to run in Windows Defender pop-up, then the installer creates the temporary folder, and when the temp folder is gone, I open the browser to double check that the update has been applied. What happens now is that I double click the installer, the spinning circle shows for one second and then nothing more, no Defender window, no temp folder. I've tried updating with 137.0.7151.119-1.1, 138.0.7204.100-1.1, and 138.0.7204.157-1.1. Run as admin does not make a difference, and running the installer does not add any events to Application or System in the Event Viewer. I could not find any other issues about this, so I'm guessing it's a local issue. What can I do to troubleshoot this and hopefully fix it? I just tried this on my other PC, which has the OS shown below, and updating there works fine, so it's a local issue on Windows 10, and perhaps even only on my device. I just tried from another local account on the Windows 10 PC, and it worked fine there as well, so it's a very local issue that only affects my main account... Any help on this is greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I just tried uninstalling to see if that made a difference, it didn't. But, since the application now was uninstalled, and I couldn't even install it the usual way, I opened CMD as admin and ran the installer. To my surprise, that worked, and it didn't even show the usual Defender pop-up. It remains to be seen if this has fixed the original issue as well. We'll see once there's a new release, but at least I might have a workaround to try the next time if the issue remains. |
Beta Was this translation helpful? Give feedback.
I just tried uninstalling to see if that made a difference, it didn't. But, since the application now was uninstalled, and I couldn't even install it the usual way, I opened CMD as admin and ran the installer. To my surprise, that worked, and it didn't even show the usual Defender pop-up.
It remains to be seen if this has fixed the original issue as well. We'll see once there's a new release, but at least I might have a workaround to try the next time if the issue remains.