New
#21
Here are the latest log files.
Please run the following commands and post the results.
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~0.0.0.0" /S
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514" /S
it may help point up the problem.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jean>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Componen
t Based Servicing\PackageIndex\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR
~0.0.0.0" /S
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\PackageIndex\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~0.0.0.0
Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514 REG_DWOR
D 0x0
C:\Users\Jean>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Componen
t Based Servicing\Packages\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1
.7601.17514" /S
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514
InstallClient REG_SZ WindowsUpdateAgent
InstallName REG_SZ Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6
.1.7601.17514.mum
InstallLocation REG_SZ \\?\C:\Windows\SoftwareDistribution\Download\a8
8203c5831df77ae060d14f2bd14310\
CurrentState REG_DWORD 0x70
SelfUpdate REG_DWORD 0x0
Visibility REG_DWORD 0x2
Trusted REG_DWORD 0x1
InstallTimeHigh REG_DWORD 0x1cc3eee
InstallTimeLow REG_DWORD 0x913fa941
InstallUser REG_SZ S-1-5-18
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Package_for_KB976933~31bf3856ad364e35~amd64~fr-FR~6.1.7601.17514
\Owners
Windows7SP1-KB976933~31bf3856ad364e35~amd64~~6.1.1.17514 REG_DWORD 0x3
0070
That looks almost the same as mine - so the problem probably lies elsewhere
The only significant difference is in the 'InstallUser' value - where yours shows the ISD for the SYSTEM account, while mine shows the value for a User account I'm not sure whether this is simply because of a potential difference in installation method - WU or standalone - or something else.
I'll have to research it and find out.
OK, on a hunch that since I have both Visual Studio 2010 x86 and Visual Studio 2010 Express (i.e. a set of them), I went ahead and uninstalled the Express. I tried to uninstall and then reinstall the Visual Studio 2010 Service Pack 1, and I got an error. And then when I tried to run Visual Studio 2010, I got an error (attached.)
Last edited by swampwiz; 03 Aug 2013 at 17:19.
VS is something I have minimal knowledge of.
If you go to the 'Uninstall a Program' listing, does the VS entry have an option to repair the current install?
I'm not familiar with VS either, but there should be that option Noel.
How are you trying to uninstall? Through Programs and features? Just right click like you have been doing to uninstall and select repair
These are the repair steps for Vista, but should work for 7You could try changing the mode of the present install: Compatibility Mode then trying the repair again.To repair the product on Windows Vista
- Click Start, click Control Panel, and then click Programs.
- Click Programs and Features and then select the Visual Studio Edition you installed.
- Click Uninstall/Change.
- In the setup wizard, select Repair or Reinstall and then click Next.
- Follow the remaining instructions in the installation wizard to finish.
Source: How to: Repair Visual Studio
If you do not see any uninstall/change, then try a new install, only this time install in https://social.technet.microsoft.com/Forums/HOW TO: Install a Software Application using Compatibility Mode
I don't think the compatibility is a problem as VS 2010 was designed for Windows 7. However I wonder if the VS 2010 that I have - the 32 bit version - is somehow wrong for my 64 bit system.
It should be fine - the problem would only come from attempting to install the 64-bit version on a 32-bit system.
I tried that compatibility trick, but it said that it could not be run in compatibility mode.