There is a hotfix version of Tortoise Git and my PC refuses to install it. It keeps saying Windows Explorer is running, even when it is not showing the Task Manager.
Is there any other way I can get this upgrade to install?
Update
I decided to start Windows 10 in Safe Mode so we can be sure that nothing is running. Yet it still would not perform the upgrade (with Administrator privileges):
I used Task Manager and I could not see gitdll.dll in the list of running processes.
1.download hotfixes
2.restart windows (don't open any apps after restart)
3.run Task Manager (from windows bar)
4.run hotfix from menu of Task Manager -- File -- Run new task
I have the same issue; I solved it by running:
listdlls64 -d "c:\Program Files\TortoiseGit\bin\gitdll.dll"
and used task manager to manually kill all processes that were using the dll, including explorer.exe. This seems entirely unnecessary but it's what worked for me.
Why so many processes (including LogonUI.exe, OpenWith.exe, splwow64.exe, etc.) attached to gitdll.dll, is unknown, and seems like an issue that can be solved. We know that explorer uses that dll, but you would think the installer/updater would expect that and be able to work around it.
In 2.10.x hotfixes there was a bug in the hotfix updater which was unable to offer a restart for replacing gitdll.dll during a restart cycle. A failure to replace this file caused lots of crashes (cf. https://tortoisegit.org/issue/3599).
Please download the full installer for TortoiseGit and install it (https://tortoisegit.org/download/; there might be a warning regarding a possible downgrade, this can be ignored).
Generally
The .MSI installer and newer hotfixes offer two options when installing:
Try to restart open processes - this might fail as described in https://stackoverflow.com/a/61026137/3906760 based on some third-party software.
Requiring no closing/restart of open programs but the replace the file on reboot. This should work in any case because the file is replaced before starting any programs using it.
I tried both types of installer:
Hotfix
Full
And both were refusing to work. I then occurred to me that all the icons were flashing on my desktop and it was stuck. This was consistent behaviour.
So I decided to switch of my Star Dock Fences:
Right-click Desktop and select Configure Fences:
Scroll-down to the bottom of the pop-up window and un-tick Enable Fences:
Close the window.
Now I was able to install the hot-fix. Interestingly the installer was only complaining about the Windows Explorer still running and did not list Fences.
I hope this helps any others who have struggles upgrading TortoiseGit.
I have successfully installed disabling AVIR and allowing the installer to close as much as it wants
Related
If not mistaken,the error occured after I misclick a notification of a antivirus software that request for a permission.My computer is using Windows 10.May I know how to solve this problem?
Older answers on this software installation:
Node.js - Cannot Install it is showing an error because of .msi
Node.js install fails on Windows 10 1803
Blocking: This sort of problem can definitely be caused by an anti-virus software blocking access to the MSI in question. Disable the anti-virus temporarily and try again. If unable to do so, perhaps try to install on a virtual machine? (for testing or real use).
Windows Installer: Just to get it out of the way: I see some recommendations to re-register the Windows Installer components, but I prefer to eliminate other causes first (a broken Windows Installer usually indicates more serious system-wide problems - such as malware infection, or full disk or something else very fundamental).
Virustotal.com: Before temporarily disabling your anti-virus (the procedure for this is obviously different for each vendor), you should verify the actual binary or MSI using the virus checker interactively and also upload the file to https://www.virustotal.com/ to make sure the MSI isn't actually infected - if it is your anti-virus is doing its job.
Re-Download: It is also a good idea to re-download the MSI from the vendor site in case it has gotten corrupted during download. This happens very frequently. I have seen days wasted with corrupted installation media the unexpected cause. Virus test this new download too using https://www.virustotal.com/ (you want to check both old and new binary for malware - the file available for download can be infected).
Other Causes: There are a number of other causes that are common for failing installers. I have several older answers on this, but maybe this is the easier one to browse: Common causes of failed installations (setup.exe or mysetup.msi fail to install). Here is a quick extract (please do visit the link):
The most common issues seem to be: security software interference, malware infected machine, corrupted download, missing runtimes, out of disk space, blocking mechanisms on the machine from corporate policies, etc...
Other Links:
WiX, deployment and setup links
I cannot reinstall node.js on windows 10
I think your problem is not from the node.js but from the Windows installer itself.
I solved mine by following the instruction here (from the Microsoft forum).
Method 1:
Perform System File Check (SFC), and then check if this fixes the issue.
Follow the steps:
a. Press “Windows Key + Q” to open Charms Bar.
b. Type “cmd” without quotes in the search box.
c. On the left pane, right-click on the “cmd” option and select “Run as Administrator”.
d. Type ‘sfc /scannow’ without quotes and hit enter.
Method 2:
I would also suggest you to run the System update readiness command. It detects incorrect manifests, cabinets or registry data, it may replace the incorrect data with corrected version available. Follow the steps.
4. Press Windows key + X.
5. Click command prompt (run as administrator).
6. In the Administrator: Command Prompt window, type the following commands. Press Enter key after each command:
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
In my case, the first method solved the problem.
I've been trying to update my server (Windows 10 Pro / 1903 Version) to version 2004 (KB3012973) through various Powershell scripts, but they all seem to apply no changes, at all, after restarting the machine.
Quite important to mention, I was successfully able to install previous updates through these scripts without any errors.
So, let me walk you through the process (PSWindowsUpdate):
First, looking for updates and using 'Install-WindowsUpdate' to install them all:
Rebooting the machine through either the script or manually by pressing on the 'Restart' button in the Start menu.
Letting the machine restart.... Then going into the Windows Update menu:
And viola! After restart, the windows version is just the same as it was before.
I have also tried running the script from the 'Searching, Downloading, and Installing Updates' tutorial by Microsoft, with no luck, as it seems.
I'd also like to note that oddly the update can be installed manually, by pressing the 'Install Now' button, which is sadly not what I'm looking for. As mentioned, the scripts have worked smoothly for previous updates.
Any help would be truly greatly appreciated!
I'm trying to use this Visual Studio extension for 2013, which recreates the built-in installer functionality from Visual Studio 2008/2010: http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx?CommentPosted=true&PageIndex=2#comments
It works, allowing me to edit the project as before. It has the install and uninstall commands when right-clicking the install project, too. It installs fine.
When I try to uninstall, though, I get the following error and then the uninstall rolls back:
Could not open key: HKEY_LOCAL_MACHINE32\SOFTWARE\Wow6432Node\Microsoft\
EAPSIMMethods\18\FastReauthContext. Verify that you have sufficient
access to that key, or contact your support personnel.
I am not doing anything with that registry key, and there don't seem to be any relevant results on google-- at least not in the normal top 5 pages. Does anyone know what causes this or how I can fix it?
While I am not able to uninstall, I am able to increment the version of the package and allow it to remove the previous install and install the new version (all at once) successfully.
I am using Windows 8.1 Pro 64 bit, the projects are compiled for <AnyCPU>, and the installer is configured for x86.
EDIT I am running Visual Studio as Admin. When uninstalling from the Control Panel, I am also clicking the 'allow' button in the UAC dialog window that pops up.
I know how to give myself access to a registry key (permissions). I want to know why this key is trying to be removed. I support this app on several machines and I don't want to have worry about remembering an uninstall hack in the future.
EDIT This only seems to be an issue for a 32x installer on a 64x OS or a Windows 8 issue. I was able to use the same 32x installer to successfully uninstall the app on a 32x Windows 7 machine.
This must be an environmental problem, that key doesn't have anything to do with installers. EAP-SIM is an authentication protocol for wireless networks. The FastReauthContext key almost surely was meant to avoid having to provide a username+password each time your machine reconnects to the network. Which makes the registry key content very sensitive of course, it can only be read by a service that runs with the System account.
So, something goofy going on with your networking setup. Verify that you can successfully reconnect to such a network. If you used a VPN before then make sure it is active again. Something like this. Update your question with anything that might be relevant to networking when you first installed the app.
I have had similar problem and what I found out this is caused by MSI attempting to delete whole "Software\Microsoft" section in the registry. Lucky you that it encounters this error and rolls everything back.
So the solution is the following:
Since you have installed your program whenever you try to uninstall it the system will run msi from cache that is usually located C:\Windows\Installer.
Find your package in the cache. Here is an article that may help you http://csi-windows.com/blog/all/27-csi-news-general/334-identifying-cached-msi-packages-in-cwindowsinstaller-without-opening-them
Open the package in Orca. You must do this as administrator.
Go to Registry table and find record with "Software\Microsoft" as a key. Most likely the Name column will contain either "-" or "*" value. This means that during uninstall MSI will try to delete whole "Software\Microsoft".
Either change the Name value to empty or "+" or try to change key to something like "Microsoft". The second option will cause that installer will not find the key to delete during uninstall, but it will skip this error and let you uninstall your program.
You installed an untested installer on your dev machine? Speaking from experience, don't do that! Snapshotted VM's are cheap and will save you from this sort of pain.
Visual Studio Deployment Projects (or VSI as it's now called ) is known for creating very poor quality installs. The combination of those two put you where you are today.
I would need to look at the full uninstall log and your MSI using ORCA to understand exactly what is going on. MSI Zap and a manual cleanup of resources is probably required at this point.
it starts up windows installer with random applications on my machine . . after i click cancel a few times, it loads vb6 fine.
any ideas why this is happening?
To stop this behavior:
Start VB6
Open the Add-Ins dialog
Uncheck the "Visual Component Manager" Add-In
Source:
After VS2010, SP1, VB6 launches VS2010 installer
This is what a Windows Installer repair looks like. It means that something is broken in one of the installed products on your system. Ideally it's a one-off repair so you might be better off letting it runs its course and do the repair, except of course if it asks for a install CD that you don't have.
The Windows event log (Application) will have MsiInstaller entries saying what product and component has the problem.
It's possible a previous installation has not completed correctly.
Use the utility at the following link to remove any rogue installations files:
http://support.microsoft.com/kb/290301 (broken link Aug.2017, leaving URL for "historical purposes").
As PhilDW has pointed out this is a Windows Installer Self-Repair issue, and can often be resolved by allowing the self-repair to complete once. At other times the problem persists and it should be fixed by other means. Even when the self-repair completes and the problem goes away, it can still resurface once you launch the conflicting application. Windows Installer is not easy to deal with.
In your particular case you might be able to get away with a "workaround" rather than a fix. By locating the main VB6 EXE file on disk (in its main installation directory) and manually creating a shortcut to it on your desktop, you might be able to successfully launch VB6 via this new shortcut without the self-repair kicking in. It might be worth a try.
This shortcut trick will not remove the underlying problem, but might help to "bypass it". Just for the record: the reason this might work is that the new, manually created shortcut is not "advertised" and will not trigger a key-path check of the installed product when launched. This is Windows Installer's way to verify that a product is correctly installed. Note that even if the workaround works, self-repair might still result during application use because of faulty COM data being detected (which is very likely the cause of the whole problem you are seeing, but give the manually created shortcut a try).
There is a rather comprehensive "article" on self-repair here: How can I determine what causes repeated Windows Installer self-repair? which might help to track down the cause of the self-repair kicking off in the first place, but fixing it can be a rather complicated process (so try the workaround first). It is a long article because there are so many different ways self-repair can occur. The common denominator is that different installers on your system are fighting over a shared setting that they keep updating with their own values on each application launch in an endless loop. The last application to launch will overwrite the registry or file system with its own setting.
This worked for me, for VS2010 RC:
"Please wait while windows configures Microsoft Visual studio 2010 Ultimate."
THe work around that fixes the issue for me was to run the following via the admin cmd prompt.
Md "%ProgramFiles(x86)%\Microsoft Visual Studio 10.0\common7\IDE\FromGAC"
from http://social.msdn.microsoft.com/Forums/en-SG/vsprereleaseannouncements/thread/572a0f8a-16b0-4e1d-b581-16be36a9b564
This was also happned to me.
Whenever i tried to open vb6, it started windows installer to configure "Autocad".
Autocad had not broken. and it was working fine.
I tried removing and reinstalling Windows Installer, But it did not solved the issue.
Then i installed Microsoft's "Windows Installer Clean Up Utility 2" from given link.
Using this utility i removed the autocad from "Windows Installers" Database.
After that VB6 never started installer again.
Keep in mind 'removing any entry from installer's database may be risky, but i had no choice. So do it on your own risk.
Download "Windows Installer Clean Up Utility 2" (this is a deprecated, unsupported and unsafe tool to use - Aug.2017. I will leave the link in for "historical purposes", don't use it).
I have a setup project created by Visual Studio 2005, and consists of both a C# .NET 2.0 project and C++ MFC project, and the C++ run time. It works properly when run from the main console, but when run over a Terminal Server session on a Windows XP target, the install fails in the following way -
When the Setup.exe is invoked, it immediately crashes before the first welcome screen is displayed. When invoked over a physical console, the setup runs normally.
I figured I could go back to a lab machine to debug, but it runs fine on a lab machine over Terminal Server.
I see other descriptions of setup problems over Terminal Server sessions, but I don't see a definite solution. Both machines have a nearly identical configuration except that the one that is failing also has the GoToMyPC Host installed.
Has anyone else seen these problems, and how can I troubleshoot this?
Thanks,
I had LOTS of issues with developing installers (and software in general) for terminal server. I hate that damn thing.
Anyway, VS Setup Projects are just .msi files, and run using the Windows installer framework.
This will drop a log file when it errors out, they're called MSIc183.LOG (swap the c183 for some random numbers and letters), and they go in your logged-in-user account's temp directory.
The easiest way to find that is to type %TEMP% into the windows explorer address bar - once you're there have a look for these log files, they might give you a clue.
Note - Under terminal server, sometimes the logs don't go directly into %TEMP%, but under numbered subdirectories. If you can't find any MSIXYZ.LOG files in there, look for directories called 1, 2, and so on, and look in those.
If you find a log file, but can't get any clues from it, post it here. I've looked at more than I care to thing about, so I may be able to help
Before installing, drop to a command prompt and type
CHANGE USER /INSTALL
Then install your software. Once the install has completed, drop back to the command prompt and type:
CHANGE USER /EXECUTE
Alternatively, don't start the installation by a double click but instead go to Add/Remove Programs and select "install software" from there.
Good luck!