"Common Setup Files 3790.0" runs EVERY TIME I start VS. I did about 4
things the other day, and I suspect one of them caused this to setup to
stick: 1) Uninstall Outlook Express 2) Uninstall Internet Explorer (from
desktop) 3) Make Mozilla default for everyting 4) Install a huge pile
of new SECURITY UPDATES from AUTOMATIC SYSTEM UPDATES.

I'll bet if I could just find the registry settings for something like a
RUN-ONCE that is checked as VS starts up, I could tweak it out of there.

Thanks in advance for any insight.

Hello Lee,

Thanks for posting. Could you look into the application event log and see
why Windows Installer has been triggered? There should be some entries for
"MsiInstaller" with detailed information. Maybe you can paste them here. I
believe they will be helpful for the troubleshooting.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[quoted text, click to view]

Hi Felix -

Don't know if these tell why, but here are all MsiInstaller entries
since BEFORE the problem:

ID 11728 - 6/1/2004 13:38
Product: Microsoft Office 2000 SR-1 Premium -- Configuration completed
successfully.

ID 11707 - 7/15/2004 6:43 MsiInstaller
Product: Java 2 Runtime Environment, SE v1.4.2_04 -- Installation
operation completed successfully.

ID 11728 - 7/17/2004 13:38
Product: Common Setup Files (3790.0) -- Configuration completed
successfully.

ID 11728 - 7/18/2004 12:03
Product: Common Setup Files (3790.0) -- Configuration completed
successfully.

ID 11728 - 7/18/2004 12:30
Product: Common Setup Files (3790.0) -- Configuration completed
successfully.

ID 11728 - 7/18/2004 12:37
Product: Common Setup Files (3790.0) -- Configuration completed
successfully.

The 11728 entries on/after 7/15 correspond to times I started Visual
Studio. Do you where VS looks for instructions to run installers as it
starts up? Do we know if 3790.0 is part of a security patch update?

Also, I took a textual snapshot of HKLM back on 5/29 and found these
entries (while search disk for txt and log files containing "3790.0").

Key Name: SOFTWARE\Classes\Installer\Products
Class Name: <NO CLASS>
Last Write Time: 11/29/2000 - 3:13 PM

Key Name:
SOFTWARE\Classes\Installer\Products\076D0CF7F75005D47A8BC22A19637080
Class Name: <NO CLASS>
Last Write Time: 3/26/2004 - 6:18 PM
Value 0
Name: AdvertiseFlags
Type: REG_DWORD
Data: 0x184

Value 1
Name: Assignment
Type: REG_DWORD
Data: 0x1

Value 2
Name: Clients
Type: REG_MULTI_SZ
Data: :


Value 3
Name: InstanceType
Type: REG_DWORD
Data: 0

Value 4
Name: Language
Type: REG_DWORD
Data: 0x409

Value 5
Name: PackageCode
Type: REG_SZ
Data: 887184B2691CE414995D8607ABBF6ADD

Value 6
Name: ProductName
Type: REG_SZ
Data: Common Setup Files (3790.0)

Value 7
Name: Version
Type: REG_DWORD
Data: 0x5020ece

----------------------------------------------------------

Key Name:
SOFTWARE\Classes\Installer\Products\E8E413EA415240F448699FF0563B28FD
Class Name: <NO CLASS>
Last Write Time: 3/26/2004 - 6:26 PM
Value 0
Name: AdvertiseFlags
Type: REG_DWORD
Data: 0x184

Value 1
Name: Assignment
Type: REG_DWORD
Data: 0x1

Value 2
Name: Clients
Type: REG_MULTI_SZ
Data: :


Value 3
Name: InstanceType
Type: REG_DWORD
Data: 0

Value 4
Name: Language
Type: REG_DWORD
Data: 0x409

Value 5
Name: PackageCode
Type: REG_SZ
Data: CD43D7C0B44791E4A84E885343CC359C

Value 6
Name: ProductName
Type: REG_SZ
Data: Core SDK (Windows Server 2003) (3790.0)

Value 7
Name: Version
Type: REG_DWORD
Data: 0x5020ece

------------------------------------------------------------

Key Name:
SOFTWARE\Microsoft\MicrosoftSDK\InstalledSDKs\44EA8771-41C9-4767-8E5F-C3490C9E8C26
Class Name: <NO CLASS>
Last Write Time: 3/26/2004 - 6:18 PM
Value 0
Name: Install Dir
Type: REG_SZ
Data: C:\Program Files\Microsoft SDK\

Value 1
Name: installer_guid
Type: REG_SZ
Data: DD668E82-FF32-4c2a-80BD-EB7E44E33A5C

Value 2
Name: propagation_date
Type: REG_SZ
Data: February 2003

Value 3
Name: title
Type: REG_SZ
Data: Common Setup Files

Value 4
Name: version
Type: REG_SZ
Data: 5.2.3790.0

Key Name:
SOFTWARE\Microsoft\MicrosoftSDK\InstalledSDKs\44EA8771-41C9-4767-8E5F-C3490C9E8C26\800662F2-9930-473B-83A1-C10C07A77967
Class Name: <NO CLASS>
Last Write Time: 3/26/2004 - 6:18 PM
Value 0
Name: dependencies
Type: REG_BINARY
Data:
00000000 3c 64 65 70 65 6e 64 65 - 6e 63 69 65 73 3e 0d 0a
<dependencies>..
00000010 09 3c 64 65 70 65 6e 64 - 65 6e 63 79 20 76 65 72
<dependency ver
00000020 73 69 6f 6e 3d 22 35 2e - 32 2e 33 37 39 30 2e 30
sion="5.2.3790.0
00000030 22 20 6f 72 6c 61 74 65 - 72 3d 22 74 72 75 65 22 "
orlater="true"
00000040 3e 44 44 36 36 38 45 38 - 32 2d 46 46 33 32 2d 34
[quoted text, click to view]
00000050 63 32 61 2d 38 30 42 44 - 2d 45 42 37 45 34 34 45
c2a-80BD-EB7E44E
00000060 33 33 41 35 43 3c 2f 64 - 65 70 65 6e 64 65 6e 63
33A5C</dependenc
00000070 79 3e 0d 0a 3c 2f 64 65 - 70 65 6e 64 65 6e 63 69
y>..</dependenci
00000080 65 73 3e es>

Value 1
Name: internal
Type: REG_BINARY
Data:
00000000 3c 69 6e 74 65 72 6e 61 - 6c 3e 0d 0a 09 3c 66 65
<internal>.. <fe
00000010 61 74 75 72 65 3e 50 53 - 44 4b 3c 2f 66 65 61 74
ature>PSDK</feat
00000020 75 72 65 3e 0d 0a 09 3c - 61 63 74 69 6f 6e 20 74 ure>..
<action t
00000030 79 70 65 3d 22 69 6e 73 - 74 61 6c 6c 22 20 77 68
ype="install" wh
00000040 65 6e 3d 22 61 66 74 65 - 72 22 3e 22 25 69 5c 73
en="after">"%i\s
00000050 65 74 75 70 5c 63 6f 6c - 72 65 67 2e 65 78 65 22
etup\colreg.exe"
00000060 20 22 25 69 5c 68 65 6c - 70 5c 70 73 64 6b 2e 68
"%i\help\psdk.h
00000070 78 63 22 3c 2f 61 63 74 - 69 6f 6e 3e 0d 0a 09 3c
xc"</action>.. <
00000080 70 72 6f 64 75 63 74 63 - 6f 64 65 3e 7b 37 46 43
productcode>{7FC
00000090 30 44 36 37 30 2d 30 35 - 37 46 2d 34 44 35 30 2d
0D670-057F-4D50-
000000a0 41 37 42 38 2d 32 43 41 - 32 39 31 33 36 30 37 30
A7B8-2CA29136070
000000b0 38 7d 3c 2f 70 72 6f 64 - 75 63 74 63 6f 64 65 3e
8}</productcode>
000000c0 3c 2f 69 6e 74 65 72 6e - 61 6c 3e </internal>

Value 2
Name: title
Type: REG_SZ
Data: Common Setup Files


Key Name:

[quoted text, click to view]

Hmmmm.... Felix, looks like you have had to deal with this before! I
found this today:
http://www.eggheadcafe.com/ng/microsoft.public.vsnet.general/post268692.asp

Will give some of this a try later. Did you ever make a Q-Article for this?

[quoted text, click to view]

Felix -

No, nothing like that at all.

Do we have any clue what the Installer is looking at, during VS startup ?

Hi Lee,

Thanks for your update. Currently I still don't think this problem is the
same as the previous one. As far as I know, the "Common Setup Files" should
be a part of the Platform SDK setup, instead of Visual Studio .Net setup.
Something is triggering Windows Installer resiliency.

Unfortunately the event log entries do not provide much information. I
expect there should be some entries like the following:

Detection of product '{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature
'dotNET_Framework_SDK', component '{03E2505A-8B35-4D3D-B581-0C41D42498A7}'
failed. The resource 'C:\Program Files\Common Files\Microsoft
Shared\Office10\MSO.DLL' does not exist.

Detection of product '{E05F0409-0E9A-48A1-AC04-E35E3033604A}', feature
'dotNET_Framework_SDK' failed during request for component
'{03E2505A-8B35-4D3D-B581-0C41D42498A7}'

These will be useful. Do we have them?

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Hi Lee,

The application event log is the most convenient way to find out what
triggers Windows Installer. If that does not offer any help, we may need to
generate some verbose installation logs for the reparation session.

However, before that, have you tried re-installing the Platform SDK? The
"Common Setup Files" should be a part of the Platform SDK installation.

Regards,

Felix Wang
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.