Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Diagnosing   (RSS)
Friday, October 23, 2009 1:01 PM

Suggestions for resolving installation errors for .NET Framework security update MS09-061

I have heard from several people over the past week or so who have had problems getting the recently released .NET Framework security update (MS09-061) to install correctly on their system when it is offered to them by Windows Update or Microsoft Update. 
Posted by astebner | 0 Comments
Wednesday, October 07, 2009 10:24 AM

Diagnosing and resolving 1935 errors for Win32 assemblies that occur on Windows Vista and later

Introduction 1935 errors can occur during an MSI-based installation while installing .NET assemblies or Win32 assemblies.  Most of the workarounds that can be found on blogs and forums (including all of the information in my 1935 error troubleshooting
Posted by astebner | 0 Comments
Thursday, March 12, 2009 9:47 PM

Steps I use to narrow down an OS update installation failure on Windows Vista and higher

A while back, I wrote a blog post describing a specific error that can occur when trying to install the .NET Framework 3.5 or 3.5 SP1 on Windows Vista and Windows Server 2008.  In that post, I talked at a high level about some of the steps I take
Posted by astebner | 4 Comments
Friday, February 06, 2009 7:24 PM

Possible solution for error 25015 with data error (cyclic redundancy check) during .NET Framework 2.0 setup

I have heard from a few people who have run into error code 25015 with a data error (cyclic redundancy check) message while trying to install the .NET Framework 2.0, 2.0 SP1 or 2.0 SP2.  This error can also occur during .NET Framework 3.0, 3.5 or
Posted by astebner | 2 Comments
Friday, January 09, 2009 5:23 PM

Steps that might help fix Windows Update errors and a blank Windows Features dialog in Windows Vista

Over the holidays, I was asked by a friend to look at a problem they were running into on their Windows Vista system. They were unable to connect to Windows Update and check for updates and received a cryptic error message. After a few minutes of poking
Posted by astebner | 1 Comments
Friday, December 12, 2008 4:55 PM

Installing .NET Framework 3.5 SP1 can succeed in cases where the .NET Framework 3.0 or 3.5 fail

I previously posted a couple of items about how to troubleshoot and work around issues in .NET Framework 3.0 and .NET Framework 3.5 setup that can be caused by failures in the ServiceModelReg.exe custom action: How to use setup log files to diagnose .NET
Posted by astebner | 1 Comments
Monday, November 24, 2008 5:02 PM

.NET Framework 3.0 and 3.5 ServiceModelReg.exe custom action failure related to files in the temporary directory

I have run into a few reports of .NET Framework 3.0 and 3.5 installation failures recently that have exhibited the same set of symptoms. I wanted to describe this issue in more detail so that folks who have followed the steps in my previous post about
Posted by astebner | 4 Comments
Monday, October 13, 2008 8:17 PM

.NET Framework cleanup and verification tools now support 2.0 SP2, 3.0 SP2 and 3.5 SP1

Right after the .NET Framework 3.5 SP1 shipped, I updated the .NET Framework cleanup tool and the .NET Framework setup verification tool to support the .NET Framework 2.0 SP2, the .NET Framework 3.0 SP2 and the .NET Framework 3.5 SP1. I updated both of
Posted by astebner | 0 Comments
Monday, October 13, 2008 7:43 PM

.NET Framework Setup Verification Tool User's Guide

.NET Framework Setup Verification Tool User's Guide Introduction This .NET Framework setup verification tool is designed to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer.
Posted by astebner | 7 Comments
Attachment(s): netfx_setupverifier_new.zip
Wednesday, September 10, 2008 6:08 PM

Possible cause of Windows Vista and Windows Server 2008 OS update failures with error code 0x8000ffff

Recently, I was helping a colleague troubleshoot an installation error in the .NET Framework 3.5 SP1 on Windows Server 2008. I wanted to describe the specific issue, and also explain how we narrowed down the issue because I think these troubleshooting
Posted by astebner | 3 Comments
Thursday, September 04, 2008 7:25 PM

Naming an assembly incorrectly when creating an MSI can cause a 1935 error with HRESULT 0x80131047

Recently, I heard from a customer who was attempting to create an MSI-based installer using WiX v3.0 . They needed to install an assembly to the global assembly cache (GAC) in their installer, but when they attempted to run their MSI, the installation
Posted by astebner | 0 Comments
Thursday, August 28, 2008 7:33 PM

.NET Framework Cleanup Tool User's Guide

.NET Framework Cleanup Tool User's Guide Introduction This .NET Framework cleanup tool is designed to automatically perform a set of steps to remove selected versions of the .NET Framework from a computer. It will remove files, directories, registry keys
Posted by astebner | 40 Comments
Attachment(s): dotnetfx_cleanup_tool.zip
Thursday, July 24, 2008 5:21 PM

Link to MSDN topic with descriptions of all Win32 error codes

I recently discovered a useful topic that was published on MSDN as a part of the Open Specifications initiative that I want to link to here in order to hopefully help make it easier to find. The topic, located at http://msdn.microsoft.com/library/cc231199.aspx
Posted by astebner | 0 Comments
Tuesday, June 24, 2008 5:41 PM

Strange .NET Framework 2.0 SP1, 3.0 SP1 and 3.5 installation error caused by orphaned registry value

Recently, I heard from a customer who could not get the .NET Framework 2.0 SP1 to install correctly on their system, and I wanted to explain the issue and how we were eventually able to resolve it in case anyone else runs into a similar issue in the future.
Posted by astebner | 5 Comments
Tuesday, June 17, 2008 8:53 AM

Information about the err.exe tool I use to look up error codes when debugging setup issues

When I am attempting to investigate a setup-related failure, I typically end up looking at verbose log files. These log files can contain information about a wide variety of failures, and the failures will typically include some detailed error information
Posted by astebner | 2 Comments
More Posts Next page »
 
Page view tracker