Uninstall unusual Google Chrome install from cmd - windows

I am working on some automation with a set of VMs. I need to use a particular template but must change the version of chrome installed on that template from automation.
So I must uninstall Chrome from the command line or a script.
Situation info:
I am trying to uninstall chrome version 75.0.3770.80
wmic does not have chrome as an installed program
Control Panel\Programs\Programs and Features does list chrome as an installed software and I can correctly uninstall it from here but only through a GUI
It is not listed in the registry under HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall
It is not listed in the registry under HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/Windows/CurrentVersion/Uninstall
The executable is in C:\Users\Administrator\AppData\Local\Google\Chrome...
the installed setup.exe is also in C:\Users\Administrator\AppData\Local\Google\Chrome\Application\75.0.3770.80\Installer
Problems:
I can't use the setup.exe installer in this location because I can not find a way of running it silently. (It has a pop up asking if you want to delete browsing data)
Deleting the executable will not remove chrome as an installed program and will not work for me
I can not find where chrome is listed in the registry and am not sure how to search for it in regedit
Any ideas of how I can uninstall this chrome version?

Related

How Can I Uninstall RStudio from Anaconda

I need to uninstall RStudio from Anaconda from my windows 10 laptop and cannot get it to work. Here is why and what I’ve tried so far.
Trying to launch RStudio Desktop (64 bit) from Anaconda I get a blank screen followed by a dialogue box asking that name a download file. This same issue documented in these three links.
failed to start rstudio (installed in Anaconda)
https://github.com/rstudio/rstudio/issues/2802
https://community.rstudio.com/t/r-does-not-launch-properly/8630
The culprit is incompatibility with the latest version of Windows 10 and the fix is not scheduled any time soon.
All posts indicate RStudio (not actually R itself although some recommend do both) needs to be un-installed and then re-installed from their respective official sites.
I tried going through Windows control panel to uninstall it, but RStudio program does not show up in the list of available apps to uninstall. (I do see R for Windows 3.4 but that’s R itself not RStudio) I searched through file explorer and see the program in my AppData/local folder with a short cut to it in my start menu. Then there are dozens of references to RStudio from within Anaconda folders.
I've searched this site and many others including Git, RStudio Community, Anaconda documentation...everything explains uninstalling R-base or how generally to uninstall packages, but nothing about RStudio.
I also tried working through these alternative suggestions from RStudio support to no avail.
https://support.rstudio.com/hc/en-us/articles/200488508-RStudio-Desktop-Will-Not-Start
What else can I try?
To uninstall R studio from Anaconda, you can go into the Anaconda environment itself. In the environment there is a setting icon ( black wheel ) on each application icon. Click on that and then remove the application.

Unable to Install Windows Azure Active Directory Module - Powershell

I'm facing a typical Microsoft bug whereby I am unable to install Windows Azure Active Directory Module Found here Windows Azure AD for Powershell
Background:
I am Running Windows 7 with Service Pack 1.
Powershell 4.0 is currently installed.
Microsoft.Net Framework 3.5.1 is checked under programs and Features
Microsoft Online Services Sign-in Assistant Both Beta and non Beta versions were installed..PC rebooted and no luck with either of them.
I have read many posts online and none of them appeared to have helped.
Does anyone know how to overcome this annoying bug.
http://blogs.technet.com/b/tune_in_to_windows_intune/archive/2013/11/09/error-when-trying-to-install-windows-azure-active-directory-module-for-windows-powershell.aspx
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/aef5669a-bc46-4c7a-9cbd-d0ed781e5190/waad-wont-install-says-signin-assistant-needs-to-be-installed-but-it-already-is?forum=WindowsAzureAD
I finally found a solution to this from Erik who posted on this site.
http://blogs.technet.com/b/tune_in_to_windows_intune/archive/2013/11/09/error-when-trying-to-install-windows-azure-active-directory-module-for-windows-powershell.aspx
Run the command prompt as an administrator by holding shift + right click on the command prompt icon, then Run as administrator.
At the command prompt
Change directories to where you AdministrationConfig-En.msi is installed.
In the command prompt type: msiexec /i AdministrationConfig-EN.msi
It will now install without the powershell warning.
Erik's commentary is that the powershell settings are only readable when privileges are elevated.
The beta version of the sign-in assistant which also needs to be installed prior to the Administrationconfig didn't help me but have helped others.
It was definitely a long and painful process.
There is a new beta version for the sign in assistant. Look up the new beta version and it will work. Just went through this about a week ago.
A String Value is "missing" in the registry. There are two potential locations in the Windows registry where PowerShell versions are stored, depending on what version or versions you have installed or possibly installed in the past.
Older version location, including Version 1.0 and 2.0:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1
Later versions location, including 5.0 and others:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\3
Each location has a sub-key called PowerShellEngine that contains a string value called PowerShellVersion.
If this value is missing in the first key mentioned above, you will receive the installation error because the installer does not look the in the second key mentioned above for the PS version.
If the value is missing, simply add it with the data of 2.0
Now installation of the AADRM will work assuming you have PS 2.0 or later installed and assuming you are using the installer version 2.50 or later of the AADRM, which does not require the sign-in assistant to be installed.

How can I get Adobe Extension Manager application path from registry through Inno Setup?

I have been looking to develop an installer that installs my extension through Inno Setup. I want to launch the Adobe Extension Manager as a post install process in the [Run] section of the Inno Setup install process. Now, there can be multiple versions of Extension Manager installed on a machine, the latest version of Extension Manager is launched by default. I want to make sure that the product version chosen by the user during installation launches the corresponding Extension Manager. Eg., if a machine has Photoshop CS5, CS6 installed, and the user chooses Photoshop CS5, then the Extension Manager CS5 should be launched. For this I want the path to the application. I am unable to get the Extension Manager path from the registry.
Problem solved!
I was able to get the path of Extension Manager by the following,
RegQueryStringValue(HKCR, 'Applications\Adobe Extension Manager CS5.exe\shell\open\command', '', path);
where path is the output string.
Thanks!

How to install a Firefox Addon with nsis

How can I install a Firefox addon via nsis installer?
When I call Firefox with the .xpi extension it doesn't work and xpi extensions are not associated with Firefox either.
If I drop it to "C:\Program Files\Mozilla Firefox\extensions" then it tries to install every single time a user opened the Firefox. Never deletes the original xpi (potentially due to the Vista UAC)
Before Firefox 3.6 you could use the -install-global-extension parameter to install an extension. However it was removed in Gecko 1.9.2. Possibly the best method to install extensions now is to create a registry entry as outlined in the Adding Extensions using the Windows Registry page.
By using the correct command line parameter :)
firefox -install-global-extension c:\extension.xpi
Refer documentation

Why does Vista not allow creation of shortcuts to "Programs" on a NonAdmin account? Not supposed to install apps from NonAdmin account?

I'm working on an installer (using Wise Installer, older version from like 1999).
I'm creating a shortcut in the Programs group to an EXE. I'm also creating a shortcut on the Desktop.
If the install is run from an Admin account, then I create the shortcut on the Common Desktop and Common Program Group (i.e., read from the HKEY_LOCAL_MACHINE\Explorer\Shellfor All Users).
If it's installed from a NonAdmin account, then I install to the HKEY_CURRENT_USER's desktop and Program Group.
Behavior
Install on:
XP NonAdmin - Desktop and Program Shortcuts install OK.
Vista Admin - Desktop & Program Shortcuts install OK.
Vista Non-Admin, UAC off- Desktop shortcut installs, but Program Shortcut does not. However, the Program group folder they're supposed to be installed to does get created.
At the end of the install, I launch the Program Group that has the shorcut. It launches in all of the above. I can manually drag a shortcut into that folder and it works just fine.
I'm bloody baffled.
I've tried installing some other commercial apps (Opera, Foxit, FireFox) Only FireFox will install under NonAdmin (and only if you select something other than Program Files, which I was aware is off limits to nonAdmin acounts). And FF doesn't install an Uninstall Icon nor
Uninstall support from the Remove Programs.
I tried installing IE 7 and it requires Admin to install. It won't even install with temporarily elevated Admin.
Perhaps the idea is that you're not supposed to install software in Vista from a NonAdmin account?
Vista does some nifty transparent redirection to provide backwards compatibility with non-vista applications. Try installing to the All Users location as a non-admin, and Vista should transparently put your shortcuts somewhere unique to that user.
I had a permissions issue with an installer I created when users started installing on Vista. What solved my problem was renaming the installer to install.exe (or setup.exe).
-Dave

Resources