Aaron Ruckman's Web Log : vista

Guidance to upgrade from Windows Vista and to Windows 7 with Visual Studio 2010 Beta 1 Installed

aaronru — Thu, 06 Aug 2009 18:04:00 GMT

Hi everyone,

The following will implement preventative measures and will avoid an unusable Visual Studio 2010 on your brand new Windows 7 OS if upgrading from Windows Vista. Please note that .NET Framework 4 Beta 2 has resolved this issue.

If you upgrade to Windows 7 from Windows Vista with the .NET Framework 4 Beta 1 installed, your machine will be in an unreliable state. In this state, Visual Studio 2010, and some managed programs depending on .NET Framework 3.5 or earlier will not work. There is no way to repair a machine that gets into this state. You will need to reinstall Windows 7.

However, uninstalling .NET Framework 4 Beta 1 before upgrading to Windows 7 alleviates this issue and upgrading should work fine. Below are detailed steps to completely remove .NET Framework 4 Beta 1 as well as Visual Studio 2010 Beta 1.

Uninstalling Visual Studio 2010 Beta 1 and .NET Framework 4 Beta 1

Perform the following steps to completely remove Visual Studio 2010 Beta 1 and the .NET Framework 4 Beta 1 from your machine.

1. Uninstall TFS Object Model (Visual Studio Team System 2010 Team Suite Beta 1 customers only)

a. Click Run from the Start Menu (or press Win+R)

b. In the Run Dialog box, type control appwiz.cpl and then click OK.

c. In the list of installed applications, select Microsoft Team Foundation Server 2010 Beta 1 Object Model and then choose Uninstall

2. Uninstall Visual Studio 2010 Beta 1

a. Click Run from the Start Menu (or press Win+R)

b. In the Run Dialog box, type control appwiz.cpl and then click OK.

c. In the list of installed applications, select an instance of Visual Studio 2010 Beta 1 (e.g. Microsoft Visual Studio Team System 2010 Team Suite Beta 1) and then choose Uninstall

d. The Wizard will load then on the Welcome screen click Next to proceed.

e. On the Maintenance page click Uninstall and choose OK to completely uninstall.

f. The Uninstall progress dialog will show the progress and then you should see the finish dialog indicating whether the uninstall was successful.

g. Reboot if prompted.

h. Repeat this step 2 for each installed version of Visual Studio 2010 Beta 1.

3. Uninstall .NET Framework 4 Beta 1

a. Click Run from the Start Menu (or press Win+R)

b. In the Run Dialog box, type control appwiz.cpl and then click OK.

c. In the list of installed applications, locate the following applications and choose Uninstall for each in this order:

i. Microsoft .NET Framework 4 Extended Beta 1 - Language Pack

ii. Microsoft .NET Framework 4 Client Profile Beta 1 - Language Pack

iii. Microsoft .NET Framework 4 Extended Beta 1

iv. Microsoft .NET Framework 4 Client Profile Beta 1

d. Reboot

4. Uninstall C++ 2010 Redistributable

a. Click Run from the Start Menu (or press Win+R)

b. In the Run Dialog box, type control appwiz.cpl and then click OK.

c. In the list of installed applications, select Microsoft Visual C++ 2010 Beta 1 Redistributable (x86 and/or x64) and then choose Uninstall

5. Reboot

6. It is now safe to start upgrading to Windows 7

When installing .NET Framework 3.5 on Vista what does the .NET Framework 2.0 SP1 on Vista error code 1058 mean and how do I work around it?

aaronru — Wed, 21 May 2008 07:41:00 GMT

If you see an error like:

[05/20/08,14:05:17] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1058

[05/20/08,14:05:17] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0

Then that is a known issue with your machine having the IIS server turned off and it needs to be turned on. The reason is that some of the ASP.NET updates require the Server to be running during install.

After installing .NET Framework 3.5 (which applies the .NET Framework 2.0 SP1 and 3.0 SP1 Updates) then you can turn the IIS server service back off.

For a more detailed description of how to find this type of error see the following:

When analyzing .NET FX 1603 errors, start with the dd_dotnetfx35install.txt log file.

Search for “1603” in the log.

In your case:

[07/17/07,13:44:29] Microsoft .NET Framework 3.5 'package': ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

Scroll up a few lines and note the name of the MSI log:

[07/17/07,13:44:09] Microsoft .NET Framework 3.5 'package': Enabling MSI log file: C:\DOCUME~1\username\LOCALS~1\Temp\dd_NET_Framework35_MSI69C8.txt

Open that log file.

Search for “return value 3”. This is what typically results in a 1603 error.

Action ended 13:44:25: InstallExecute. Return value 3.

Scroll up a few lines to see the actual error:

07/17/07 13:44:24 DDSet_Error: The Commandline '"C:\WINDOWS\Microsoft.NET\Framework\v3.5\WFServicesReg.exe" /c /v /m /i' returned non-zero value: -2147023838.

In this case, there is more:

DDSet_Warning: CScriptMapsComponent::Initialize m_spAdminBase.CoCreateInstance failed. Error code: 0x80070422

DDSet_Warning: CFxInstaller::SetupScriptMapsIIS6 Failed to initialize IIS6 APIs. Error code: 0x80070422

DDSet_Status: CScriptMapsComponent::Close

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070422

Find out what the error code means:

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x422

# for decimal 1058 / hex 0x422

ERROR_SERVICE_DISABLED winerror.h

# The service cannot be started, either because it is

# disabled or because it has no enabled devices associated

# with it.

# 1 matches found for "-2147023838"

The installation needs the IIS Service running on your machine.

.NET Framework 3.0 SP1 & 2.0 SP1 on Vista RTM?

aaronru — Mon, 21 Jan 2008 06:14:00 GMT

I've received the following type of question a few times and would like to give the answer with some background:

Q. Where is the .NET Framework 3.0 SP1 & 2.0 SP1 for Vista RTM?

A. .NET Framework 3.0 & 2.0 released with Vista as OS Windows Components, which means that they are serviced as any other windows Component. Therefore, the .NET Framework 3.0 & 2.0 Service packages will be officially released as part of the Vista Service packages. When Vista SPX is shipped then .NET Framework 2.0 & 3.0 might also include updates in that service package.

In this case the .NET Framework 3.0 & 2.0 have a service package that will be shipped with Vista SP1. Vista SP1 RC is available now (http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx)

NOTE: The same logic stated for Vista and .NET Framework will also be true for Windows2008 & .NET Framework 2.0 & 3.0, only Windows Server2008 will release with .NET Framework 2.0 SP1 & 3.0 SP1 in the OS.

Recent .NET Framework KBs enumerated

aaronru — Thu, 03 Jan 2008 02:21:00 GMT

With .NET Framework 3.5 on Vista or LHS you might get one of the following KBs installed. The following table helps to identify which KB matches what Framework version and which language.

LCID = Language Code ID.

NetFx2.0 SP1 & NetFx3.0 SP1 = These KBs are the representation for the Language enabling packages.

The English + CORE packages must be present prior to installing an additional language package.
The non-English KBs are included in the appropriate 3.5 language package.

2.0 & 3.0 RTM Stand Alone Language Pack = These KBs enable Users to install a .NET Framework Language on Vista or LHS when the OS Language package, which contains the 2.0 & 3.0 RTM, is not installed.

These are included in the 3.5 Language packages and installed as appropriate.
Note that the 936704 & 936705 are not necessary, as 110806 and 929300 contain all of the relevant files anyway.

LCID	Language	NetFx2.0 SP1	2.0 RTM STAND ALONE LANG Pack	NetFx3.0 SP1	3.0 RTM STAND ALONE LANG Pack
1033	English+CORE	110806	936704	929300	936705
1041	Japanese	935953	936382	935952	936428
1031	German	936360	936383	936406	936429
1036	French	936361	936384	936407	936430
1028	Chinese (Traditional)	936362	936385	936408	936431
2052	Chinese (Simplified)	936363	936386	936409	936432
1042	Korean	936364	936387	936410	936433
3082	Spanish	936365	936388	936411	936434
1040	Italian	936366	936389	936412	936435
1025	Arabic	936367	936390	936413	936436
1046	Brazilian Portuguese	936368	936391	936414	936437
2070	Portuguese	936369	936392	936415	936438
1029	Czech	936370	936393	936416	936439
1030	Danish	936371	936394	936417	936440
1043	Dutch	936372	936395	936418	936441
1035	Finnish	936373	936396	936419	936442
1032	Greek	936374	936398	936420	936443
1037	Hebrew	936375	936399	936421	936444
1038	Hungarian	936376	936400	936422	936445
1044	Norwegian	936377	936401	936423	936446
1045	Polish	936378	936402	936424	936447
1049	Russian	936379	936403	936425	936448
1053	Swedish	936380	936404	936426	936449
1055	Turkish	936381	936405	936427	936450

.NET Framework Error: 6015 - EFS is disabled

aaronru — Tue, 14 Aug 2007 17:32:00 GMT

If you are installing the .NET Framework 3.5 Beta2 on Vista and you get an error message like:

Installer encountered an error: 0x8007177f. This machine is disabled for file encryption"

Then what has happened is that your Domain administrator has disabled per policy the ability to have file encryption.

The following site explains how to correct this issue.

http://support.microsoft.com/kb/933595

Possible issue using ASP.NET controls in VS 2008 beta 2

aaronru — Tue, 07 Aug 2007 19:51:00 GMT

Description of this issue

Since Visual Studio 2008 beta 2 and the .NET Framework 3.5 beta 2 were released, we have heard of a few issues related to using ASP.NET controls in the VS IDE after installing beta 2. The issues we have seen so far include the following:

ASP.NET controls do not show up in the Visual Studio 2008 beta 2 toolbox
ASP.NET tag IntelliSense and schema validation is broken in HTML source view in the VS IDE

In the cases we've seen so far, the systems are running Windows Vista, and the file version of %windir%\Microsoft.NET\Framework\v2.0.50727\system.web.dll is less than the official beta 2 version of 2.0.50727.1378.

How to workaround this issue

If you run into an issue like this, you can uninstall .NET Framework 2.0 hotfixes and then re-install the .NET Framework 3.5 as a workaround.

There are some detailed instructions that explain how to do this at this location, including a list of the exact hotfixes that need to be uninstalled to resolve this issue.

You do not need to re-install the previous hotfixes after working around this issue. The .NET Framework 2.0 SP1 and 3.0 SP1 hotfix packages that are installed as prerequisites for the .NET Framework 3.5 beta 2 already include all of the fixes that were previously released as separate Windows Vista hotfixes for the .NET Framework 2.0/3.0.

Root cause of this issue

We have found a problem with how some Windows Vista-specific hotfixes for the .NET Framework 2.0 have been packaged in the past that can cause an incorrect version of files like system.web.dll to appear on the system. This means that if you have some specific .NET Framework 2.0 hotfixes installed on your Windows Vista system, you might encounter this type of file version problem and therefore also run into some issues when trying to use VS 2008 beta 2. Windows Vista is built from components, and these components have their own version information that is used to determine which files will be present on the OS. The versions of the files contained in each of the components does not have to match the component version, and that can lead to newer versions of components having older versions of files in some cases such as this.

How do I get that annoying Visual Studio compatiblity dialog to go away when running on Vista

aaronru — Tue, 17 Apr 2007 08:33:00 GMT

When using whidbey you might see a compatibility dialog. This dialog can be remedied by installing the Visual Studio's Vista Patch:

http://go.microsoft.com/?linkid=6366078

For more information:

http://msdn2.microsoft.com/en-us/vstudio/aa948853.aspx

After installing the patch, you will then be able check the box in the right way to not see that compatibility dialog again. :-)