try to remove all previous versions of .net 2.0 and 3.x
Then reinstall
Main Topics
Browse All Topics
Loading Advertisement...
Question
Cannot install Visual C# 2008 Express Edition on my computer
OS: Microsoft Windows XP Professional Version 2002 Service Pack 2
I have resolved some of the issues regarding the installation, but the install still fails.
First I execute the downloaded file "vcssetup.exe". This brings up a wizard. I just leave all the default choices, and proceed to install. It makes progress, but then I get this error message:
Microsoft Visual C# 2008 Express Edition Setup
Error occurred during setup
Setup could not install the following component:
Microsoft.NET Framework 3.5
Setup did not attempt to install the following components:
(The other components are listed)
I have tried to resolve this myself by Googling with the error messages. I was able to resolve a few issues, like ASP not being started, by looking at the Event Viewer.
Now, when I look at Event Viewer, I get this message:
The server {8BC3F05E-D86B-11D0-A075-0
One suggestion offered on the Internet was to download a new version of Windows Update, which I did. After rebooting, I get the same error.
I'm waiting for suggestions on how to resolve this. Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Subscribe now for full access to Experts Exchange and get
Instant Access to this Solution
- Plus...
- 30 Day FREE access, no risk, no obligation
- Collaborate with the world's top tech experts
- Unlimited access to our exclusive solution database
- Never be left without tech help again
Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.
- "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
- "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
- "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.
See what Experts Exchange can do for you.
Got a question?
We've got the answer.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
Need individual assistance?
Our experts are ready to help.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Want to learn from the best?
Read articles from industry experts.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Working on a long term project?
Store your work and research.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Trusted by the world's most respected brands.
Faithfully serving IT professionals since 1996.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Free Tech Articles
-
WARNING: 5 Reasons why you should NEVER fix a computer for free.
It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
-
SCCM OSD Basic troubleshooting
SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
-
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
-
Create a Win7 Gadget
This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
-
Outlook continually prompting for username and password
There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
-
Backup Exchange 2010 Information Store using Windows Backup
There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...
Cloud Class Webinars
- Avoiding Bugs in Microsoft Access
Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
- Top 10 Best New Features in Visio 2010
Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
- IT Consultant Business Secrets Revealed
Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
- Disaster Recovery and Business Continuity
Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
- Organize Your Visio Diagrams with Containers and Lists
Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
- How to Us Objects, Properties, Events and Methods in Microsoft Access
Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Answers
ororiole, I did try that, but I got the same error. That was a good suggestion, though. The problem remains with .NET 3.5 itself.
jaime_olivares, there were no other versions of .NET installed on my machine.
graye, I took a quick look at that link, and I got instantly sleep-deprived reading all about WMI. But now that I've had a good night's rest, I'll try again. Thanks. I'll get back here to post the results.
OK, graye, I ran WMIDiag. Here is the entire report produced by WMIDiag:
-------- BEGIN WMIDiag Report -----------------
.1571 13:04:18 (0) ** WMIDiag v2.0 started on Wednesday, August 06, 2008 at 12:58.
.1572 13:04:18 (0) **
.1573 13:04:18 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1574 13:04:18 (0) **
.1575 13:04:18 (0) ** This script is not supported under any Microsoft standard support program or service.
.1576 13:04:18 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1577 13:04:18 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1578 13:04:18 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1579 13:04:18 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1580 13:04:18 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1581 13:04:18 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1582 13:04:18 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1583 13:04:18 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1584 13:04:18 (0) ** of the possibility of such damages.
.1585 13:04:18 (0) **
.1586 13:04:18 (0) **
.1587 13:04:18 (0) ** --------------------------
.1588 13:04:18 (0) ** --------------------------
.1589 13:04:18 (0) ** --------------------------
.1590 13:04:18 (0) **
.1591 13:04:18 (0) ** --------------------------
.1592 13:04:18 (0) ** Windows XP - Service pack 2 - 32-bit (2600) - User 'LEONARD-OWFLWFZ\LEN' on computer 'LEONARD-OWFLWFZ'.
.1593 13:04:18 (0) ** --------------------------
.1594 13:04:18 (0) ** Environment: ..........................
.1595 13:04:18 (0) ** There are no missing WMI system files: ..........................
.1596 13:04:18 (1) !! ERROR: The following WMI repository file(s) is/are missing: ..........................
.1597 13:04:18 (0) ** - MAPPING.VER
.1598 13:04:18 (0) ** - MAPPING1.MAP
.1599 13:04:18 (0) ** - MAPPING2.MAP
.1600 13:04:18 (0) ** => To fix this issue:
.1601 13:04:18 (0) ** - ENSURE you have all access rights to the WMI repository folder.
.1602 13:04:18 (0) ** - ENSURE you run WMIDiag as an Administrator.
.1603 13:04:18 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
.1604 13:04:18 (0) ** the WMI service successfully started, then WMI will rebuild the repository based on the
.1605 13:04:18 (0) ** auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
.1606 13:04:18 (0) ** of WMIDiag. Check WMIDiag LOG.
.1607 13:04:18 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
.1608 13:04:18 (0) ** the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
.1609 13:04:18 (0) ** You must fix those issues first!
.1610 13:04:18 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
.1611 13:04:18 (0) ** the WMI repository, then you must restore the WMI repository from a previous backup.
.1612 13:04:18 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1613 13:04:18 (0) ** of the WMI repository.
.1614 13:04:18 (0) ** => If no backup is available, you must rebuild the repository.
.1615 13:04:18 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1616 13:04:18 (0) ** otherwise some applications may fail after the reconstruction.
.1617 13:04:18 (0) ** This can be achieved with the following command:
.1618 13:04:18 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1619 13:04:18 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1620 13:04:18 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1621 13:04:18 (0) ** This may imply the lost of WMI registration information.
.1622 13:04:18 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1623 13:04:18 (0) ** ALL fixes previously mentioned.
.1624 13:04:18 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1625 13:04:18 (0) ** => To rebuild the WMI repository, you must:
.1626 13:04:18 (0) ** - Stop the WMI Service.
.1627 13:04:18 (0) ** i.e. 'NET.EXE STOP WINMGMT'
.1628 13:04:18 (0) ** - Move the existing WMI repository files to another location.
.1629 13:04:18 (0) ** i.e. MOVE C:\WINDOWS\SYSTEM32\WBEM\R
.1630 13:04:18 (0) ** - Start the WMI Service.
.1631 13:04:18 (0) ** i.e. 'NET.EXE START WINMGMT'
.1632 13:04:18 (0) ** WMI will rebuild the WMI repository based the auto-recovery mechanism.
.1633 13:04:18 (0) **
.1634 13:04:18 (0) ** WMI repository state: ..........................
.1635 13:04:18 (0) ** BEFORE running WMIDiag:
.1636 13:04:18 (0) ** The WMI repository has a size of: ..........................
.1637 13:04:18 (0) ** - Disk free space on 'C:': ..........................
.1649 13:04:18 (0) ** --------------------------
.1650 13:04:18 (2) !! WARNING: Windows Firewall Service: ..........................
.1651 13:04:18 (0) ** --------------------------
.1652 13:04:18 (0) ** DCOM Status: ..........................
.1653 13:04:18 (0) ** WMI registry setup: ..........................
.1654 13:04:18 (0) ** INFO: WMI service has dependents: ..........................
.1655 13:04:18 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1656 13:04:18 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1657 13:04:18 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1658 13:04:18 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
.1659 13:04:18 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
.1660 13:04:18 (0) ** this can prevent the service/application to work as expected.
.1661 13:04:18 (0) **
.1662 13:04:18 (0) ** RPCSS service: ..........................
.1663 13:04:18 (0) ** WINMGMT service: ..........................
.1664 13:04:18 (0) ** => The WINMGMT service can't be started. This could be due to the following reasons:
.1665 13:04:18 (0) ** - The service is DISABLED. You can re-enable the service with the command:
.1666 13:04:18 (0) ** i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1667 13:04:18 (0) ** Note: The SC.EXE command is available in the Windows Resource Kit.
.1668 13:04:18 (0) ** - The WINMGMT service depends on RPCSS service which is DISABLED or unable to start.
.1669 13:04:18 (0) ** - If the service is ENABLED but can't start, then the service registry may contains bad data.
.1670 13:04:18 (0) ** Note: Registry setup errors should be reported. Follow the steps related to registry issues.
.1671 13:04:18 (0) ** => After verifying the registry, if the WMI service does not start yet, you can try to
.1672 13:04:18 (0) ** to run the service as a STANDALONE service host or as a SHARED service host (SvcHost)
.1673 13:04:18 (0) ** You can achieve this by running ONE of the following commands (case sensitive):
.1674 13:04:18 (0) ** - to configure the service to run as a SHARED service host (recommended):
.1675 13:04:18 (0) ** i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\W
.1676 13:04:18 (0) ** - if you have issue to get it running as a SHARED service host, the WMI service
.1677 13:04:18 (0) ** can be configured to run as a STANDALONE service host:
.1678 13:04:18 (0) ** i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\W
.1679 13:04:18 (0) ** => If the registry is correct and the WMI service does not start yet, the WMI repository could be inconsistent.
.1680 13:04:18 (0) ** - Under Windows XP SP2, you can validate the repository consistency by:
.1681 13:04:18 (0) ** executing the following command:
.1682 13:04:18 (0) ** i.e. 'WMIDiag CheckConsistency'
.1683 13:04:18 (0) ** Note: Under Windows XP SP2, when the repository is checked and detected INCONSISTENT,
.1684 13:04:18 (0) ** a new repository is automatically re-created based on Auto-Recovery mechanism.
.1685 13:04:18 (0) ** Note that some information can be lost during this process (i.e. static data, CIM registration).
.1686 13:04:18 (0) ** However, the original repository is located at 'C:\WINDOWS\SYSTEM32\WBEM\
.1687 13:04:18 (0) ** The computer must be rebooted for the system to work with the re-created repository.
.1688 13:04:18 (0) ** - The repository can be recovered from a previous backup.
.1689 13:04:18 (0) ** Note: The System State backup or the System Restore snapshot contain a backup of
.1690 13:04:18 (0) ** of the WMI repository.
.1691 13:04:18 (0) ** => If no backup is available, you must rebuild the repository.
.1692 13:04:18 (0) ** - Re-run WMIDiag with the ShowMOFErrors, this will show any MOF file issues.
.1693 13:04:18 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1694 13:04:18 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1695 13:04:18 (0) ** otherwise some applications may fail after the reconstruction.
.1696 13:04:18 (0) ** This can be achieved with the following command:
.1697 13:04:18 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.1698 13:04:18 (0) ** Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1699 13:04:18 (0) ** registry key will be excluded from the WMI repository reconstruction.
.1700 13:04:18 (0) ** This may imply the lost of WMI registration information.
.1701 13:04:18 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1702 13:04:18 (0) ** ALL fixes previously mentioned.
.1703 13:04:18 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1704 13:04:18 (0) ** - To rebuild the WMI repository, you must:
.1705 13:04:18 (0) ** - Stop the WMI Service.
.1706 13:04:18 (0) ** i.e. 'NET.EXE STOP WINMGMT'
.1707 13:04:18 (0) ** - Move the existing WMI repository files to another location.
.1708 13:04:18 (0) ** i.e. MOVE C:\WINDOWS\SYSTEM32\WBEM\R
.1709 13:04:18 (0) ** - Start the WMI Service.
.1710 13:04:18 (0) ** i.e. 'NET.EXE START WINMGMT'
.1711 13:04:18 (0) ** WMI will rebuild the WMI repository based the auto-recovery mechanism.
.1712 13:04:18 (0) **
.1713 13:04:18 (0) ** --------------------------
.1714 13:04:18 (0) ** WMI service DCOM setup: ..........................
.1715 13:04:18 (0) ** WMI components DCOM registrations: ..........................
.1716 13:04:18 (0) ** WMI ProgID registrations: ..........................
.1717 13:04:18 (0) ** WMI provider DCOM registrations: ..........................
.1718 13:04:18 (0) ** WMI provider CIM registrations: ..........................
.1719 13:04:18 (0) ** WMI provider CLSIDs: ..........................
.1720 13:04:18 (0) ** WMI providers EXE/DLL availability: ..........................
.1721 13:04:18 (0) ** --------------------------
.1722 13:04:18 (0) ** Overall DCOM security status: ..........................
.1723 13:04:18 (0) ** Overall WMI security status: ..........................
.1724 13:04:18 (0) ** - Started at 'Root' --------------------------
.1725 13:04:18 (0) ** WMI permanent SUBSCRIPTION(S): ..........................
.1726 13:04:18 (0) ** WMI TIMER instruction(s): ..........................
.1727 13:04:18 (1) !! ERROR: WMI ADAP status: ..........................
.1728 13:04:18 (0) ** You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1729 13:04:18 (0) ** the performance counters with the WMI performance classes with the following commands:
.1730 13:04:18 (0) ** i.e. 'WINMGMT.EXE /CLEARADAP'
.1731 13:04:18 (0) ** i.e. 'WINMGMT.EXE /RESYNCPERF'
.1732 13:04:18 (0) ** The ADAP process logs informative events in the Windows NT event log.
.1733 13:04:18 (0) ** More information can be found on MSDN at:
.1734 13:04:18 (0) ** http://msdn.microsoft.com/
.1735 13:04:18 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: ..........................
.1736 13:04:18 (0) ** - Root, 0x1AD - ActiveX component can't create object.
.1737 13:04:18 (0) **
.1738 13:04:18 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: ..........................
.1739 13:04:18 (0) ** - Root, 0x80080005 - Server execution failed.
.1740 13:04:18 (0) ** - Root, 0x80080005 - Server execution failed.
.1741 13:04:18 (0) ** - Root/Default, 0x80080005 - Server execution failed.
.1742 13:04:18 (0) ** - Root/CIMv2, 0x80080005 - Server execution failed.
.1743 13:04:18 (0) ** - Root/WMI, 0x80080005 - Server execution failed.
.1744 13:04:18 (0) **
.1745 13:04:18 (0) ** WMI GET operations: ..........................
.1746 13:04:18 (0) ** WMI MOF representations: ..........................
.1747 13:04:18 (0) ** WMI QUALIFIER access operations: ..........................
.1748 13:04:18 (0) ** WMI ENUMERATION operations: ..........................
.1749 13:04:18 (0) ** WMI EXECQUERY operations: ..........................
.1750 13:04:18 (0) ** WMI GET VALUE operations: ..........................
.1751 13:04:18 (0) ** WMI WRITE operations: ..........................
.1752 13:04:18 (0) ** WMI PUT operations: ..........................
.1753 13:04:18 (0) ** WMI DELETE operations: ..........................
.1754 13:04:18 (0) ** WMI static instances retrieved: ..........................
.1755 13:04:18 (0) ** WMI dynamic instances retrieved: ..........................
.1756 13:04:18 (0) ** WMI instance request cancellations (to limit performance impact): ..........................
.1757 13:04:18 (0) ** --------------------------
.1758 13:04:18 (0) **
.1759 13:04:18 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is external to WMI.
.1760 13:04:18 (0) **
.1761 13:04:18 (0) ** 5 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
.1762 13:04:18 (0) ** --------------------------
.1763 13:04:18 (0) ** WMI Registry key setup: ..........................
.1764 13:04:18 (0) ** --------------------------
.1765 13:04:18 (0) ** --------------------------
.1766 13:04:18 (0) ** --------------------------
.1767 13:04:18 (0) ** --------------------------
.1768 13:04:18 (0) **
.1769 13:04:18 (0) ** --------------------------
.1770 13:04:18 (0) ** --------------------------
.1771 13:04:18 (0) ** --------------------------
.1772 13:04:18 (0) **
.1773 13:04:18 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\LEN.LEONARD-OWFLW
.1774 13:04:18 (0) **
.1775 13:04:18 (0) ** WMIDiag v2.0 ended on Wednesday, August 06, 2008 at 13:04 (W:28 E:23 S:1).
-------- END WMIDiag Report -----------------
I will try some of the suggestions in that report, when I get a little time later on today. I'll report back here with the results. Thanks, that WMIDiag is revealing!
So, the WMI repository is corrupted... one of the easiest (but very crude) way to rebuild the repository is to just rename the directory where the repository lives, and let it rebuild itself on it's own. This is typically a "last resort" approach, so I'd try the other suggestions in the report first. But, if you're left with no other option, the following will do the trick
Net Stop WinMgmt /y
Ren %WinDir%\System32\Wbem\Rep
Net Start WinMgmt /y
graye, I was unable to resolve the problem any other way, other than doing the "last resort" method you mentioned in your last post. Then I ran the following 2 commands, as suggested in the WMIDiag documentation:
RUNDLL32.EXE C:\WINDOWS\SYSTEM32WBEM\WM
WMIDiag CheckConsistency
The last command produced a message file. I have taken the following excerpts from that file, which point to errors which I don't know how to resolve:
..203 16:47:42 (0) ** Verifying WMI Repository files presence.
..204 16:47:42 (1) !! ERROR: (CheckWMIRepositoryFiles) : 0x4C - Path not found. Folder 'C:\WINDOWS\SYSTEM32\WBEM\
..205 16:47:42 (1) !! ERROR: Unable to access or find file 'INDEX.BTR'.
..206 16:47:42 (1) !! ERROR: Unable to access or find file 'INDEX.MAP'.
..207 16:47:42 (1) !! ERROR: Unable to access or find file 'MAPPING.VER'.
..208 16:47:42 (1) !! ERROR: Unable to access or find file 'MAPPING1.MAP'.
..209 16:47:42 (1) !! ERROR: Unable to access or find file 'MAPPING2.MAP'.
..210 16:47:42 (1) !! ERROR: Unable to access or find file 'OBJECTS.DATA'.
..211 16:47:42 (1) !! ERROR: Unable to access or find file 'OBJECTS.MAP'.
..212 16:47:42 (0) ** Verifying additional binaries in WBEM folder.
..213 16:47:43 (0) ** Verifying Auto-Recovery MOF files presence.
..214 16:47:43 (4) Reading registry (REG_MULTI_SZ) 'HKLM\SOFTWARE\Microsoft\W
..215 16:47:43 (0) ** Verifying MOF files in WBEM folder.
..216 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..217 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..218 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..219 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..220 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..221 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..222 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..223 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..224 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..225 16:47:43 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..226 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..227 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..228 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..229 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..230 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..231 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..232 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..233 16:47:44 (3) 'C:\WINDOWS\SYSTEM32\WBEM\
..234 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..235 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..236 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..237 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..238 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..239 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..240 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..241 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..242 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..243 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..244 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..245 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..246 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..247 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..248 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..249 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..250 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..251 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..252 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..253 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..254 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..255 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..256 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..257 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..258 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..259 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..260 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..261 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..262 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..263 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..264 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..265 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..266 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..267 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..268 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..269 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..270 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..271 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..272 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..273 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..274 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..275 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..276 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..277 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..278 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..279 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..280 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..281 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..282 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..283 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..284 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..285 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..286 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..287 16:47:44 (1) !! ERROR: Unable to access or find file 'C:\1C0DCDC39C46E51DD6E0C8
..288 16:47:44 (3) Found 'C:\WINDOWS\SYSTEM32\WBEM\
..289 16:47:44 (1) !! ERROR: Unable to access or find file 'C:\WINDOWS\SYSTEM32\WBEM\
..290 16:47:44 (0) ** Verifying '#PRAGMA AUTORECOVER' statement in MOF files.
..291 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..292 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..293 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..294 16:47:46 (3) => Only the MOF statements and logic will determine if the MOF is a true UNINSTALL MOF.
..295 16:47:46 (3) A true UNINSTALL MOF should NOT contain the '#PRAGMA AUTORECOVER' statement and should NOT be included in the AUTORECOVER LIST.
..296 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..297 16:47:46 (3) => Only the MOF statements and logic will determine if the MOF is a true UNINSTALL MOF.
..298 16:47:46 (3) A true UNINSTALL MOF should NOT contain the '#PRAGMA AUTORECOVER' statement and should NOT be included in the AUTORECOVER LIST.
..299 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..300 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..301 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..302 16:47:46 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..303 16:47:47 (2) !! WARNING: MOF file 'C:\WINDOWS\SYSTEM32\WBEM\
..304 16:47:47 (3) => Only the MOF statements and logic will determine if the MOF is a true UNINSTALL MOF.
..305 16:47:47 (3) A true UNINSTALL MOF should NOT contain the '#PRAGMA AUTORECOVER' statement and should NOT be included in the AUTORECOVER LIST.
.
.
.
.1279 16:47:56 (3) WMI registry key (REG_DWORD) 'NextInstance' is correct.
.1280 16:47:56 (3) 'Windows Management Instrumentation' service registered correctly (WINMGMT).
.1281 16:47:56 (0) ** Verifying WMI Service known dependents.
.1282 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1283 16:47:56 (4) Reading registry (REG_MULTI_SZ) 'HKLM\SYSTEM\CurrentContro
.1284 16:47:56 (4) Reading registry (REG_DWORD) 'HKLM\SYSTEM\CurrentContro
.1285 16:47:56 (2) !! WARNING: 'Security Center' (WSCSVC, StartMode='Automatic') is installed depends on WMI Service.
.1286 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1287 16:47:56 (4) Reading registry (REG_MULTI_SZ) 'HKLM\SYSTEM\CurrentContro
.1288 16:47:56 (4) Reading registry (REG_DWORD) 'HKLM\SYSTEM\CurrentContro
.1289 16:47:56 (2) !! WARNING: 'Windows Firewall/Internet Connection Sharing (ICS)' (SHAREDACCESS, StartMode='Automatic') is installed depends on WMI Service.
.1290 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1291 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1292 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1293 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1294 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1295 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1296 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1297 16:47:56 (4) Reading registry (REG_SZ) 'HKLM\SYSTEM\CurrentContro
.1298 16:47:56 (0) ** Verifying 'RPCSS' service status.
.1299 16:47:56 (3) Verifying 'RPCSS' service started state.
.1300 16:47:56 (3) 'RPCSS' service IS started.
.1301 16:47:56 (0) ** Verifying 'WINMGMT' service status.
.1302 16:47:56 (3) Verifying 'WINMGMT' service started state.
.1303 16:47:56 (3) 'WINMGMT' service is NOT started.
.1304 16:47:57 (3) Verifying 'WINMGMT' service started state.
.1305 16:47:57 (3) 'WINMGMT' service is NOT started.
.1306 16:47:57 (3) Verifying 'WINMGMT' service started state.
.1307 16:47:57 (3) 'WINMGMT' service is NOT started.
.1308 16:47:58 (3) Verifying 'WINMGMT' service started state.
.1309 16:47:58 (3) 'WINMGMT' service is NOT started.
.1310 16:47:58 (3) Verifying 'WINMGMT' service started state.
.1311 16:47:58 (3) 'WINMGMT' service is NOT started.
.1312 16:47:59 (3) Verifying 'WINMGMT' service started state.
.1313 16:47:59 (3) 'WINMGMT' service is NOT started.
.1314 16:47:59 (3) Verifying 'WINMGMT' service started state.
.1315 16:47:59 (3) 'WINMGMT' service is NOT started.
.1316 16:48:00 (3) Verifying 'WINMGMT' service started state.
.1317 16:48:00 (3) 'WINMGMT' service is NOT started.
.1318 16:48:00 (3) Verifying 'WINMGMT' service started state.
.1319 16:48:00 (3) 'WINMGMT' service is NOT started.
.1320 16:48:01 (3) Verifying 'WINMGMT' service started state.
.1321 16:48:01 (3) 'WINMGMT' service is NOT started.
.1322 16:48:01 (3) Verifying 'WINMGMT' service started state.
.1323 16:48:01 (3) 'WINMGMT' service is NOT started.
.1324 16:48:02 (3) Verifying 'WINMGMT' service started state.
.1325 16:48:02 (3) 'WINMGMT' service is NOT started.
.1326 16:48:02 (3) Verifying 'WINMGMT' service started state.
.1327 16:48:02 (3) 'WINMGMT' service is NOT started.
.1328 16:48:03 (3) Verifying 'WINMGMT' service started state.
.1329 16:48:03 (3) 'WINMGMT' service is NOT started.
.1330 16:48:03 (3) Verifying 'WINMGMT' service started state.
.1331 16:48:03 (3) 'WINMGMT' service is NOT started.
.1332 16:48:04 (3) Verifying 'WINMGMT' service started state.
.1333 16:48:04 (3) 'WINMGMT' service is NOT started.
.1334 16:48:04 (3) Verifying 'WINMGMT' service started state.
.1335 16:48:04 (3) 'WINMGMT' service is NOT started.
.1336 16:48:05 (3) Verifying 'WINMGMT' service started state.
.1337 16:48:05 (3) 'WINMGMT' service is NOT started.
.1338 16:48:05 (3) Verifying 'WINMGMT' service started state.
.1339 16:48:05 (3) 'WINMGMT' service is NOT started.
.1340 16:48:06 (3) Verifying 'WINMGMT' service started state.
.1341 16:48:06 (3) 'WINMGMT' service is NOT started.
.1342 16:48:06 (3) Verifying 'WINMGMT' service started state.
.1343 16:48:06 (3) 'WINMGMT' service is NOT started.
.1344 16:48:07 (3) Verifying 'WINMGMT' service started state.
.1345 16:48:07 (3) 'WINMGMT' service is NOT started.
.1346 16:48:07 (1) !! ERROR: (StartService) : Start service 'WINMGMT' command timeout.
.1347 16:48:07 (0) ** Verifying WMI repository consistency.
.1348 17:18:35 (1) !! ERROR: (CheckWMIRepositoryConsist
.1349 17:18:35 (0) ** Verifying WMI providers loaded BEFORE WMIDiag execution.
.1350 17:19:05 (1) !! ERROR: (CheckWMIStaticData) : 0x80080005 - Server execution failed
.1351 17:19:05 (0) ** Verifying WMI namespace 'Root' (L=1).
.1352 17:19:35 (1) !! ERROR: (CheckWMIStaticData) : 0x1AD - ActiveX component can't create object
.1353 17:20:05 (1) !! ERROR: (CheckWMIStaticData) : 0x80080005 - Server execution failed
.1354 17:20:05 (0) ** Verifying WMI ADAP status.
.1355 17:20:35 (1) !! ERROR: (GetADAPStatus) : 0x80080005 - Server execution failed
.1356 17:20:35 (0) ** Verifying WMI features.
.1357 17:20:35 (3) Opening WMI namespace 'Root'.
.1358 17:21:05 (1) !! ERROR: (CheckWMIFeatures) : 0x80080005 - Server execution failed
.1359 17:21:05 (3) Opening WMI namespace 'Root/Default'.
.1360 17:21:35 (1) !! ERROR: (CheckWMIFeatures) : 0x80080005 - Server execution failed
.1361 17:21:35 (3) Opening WMI namespace 'Root/CIMv2'.
.1362 17:22:05 (1) !! ERROR: (CheckWMIFeatures) : 0x80080005 - Server execution failed
.1363 17:22:05 (3) Opening WMI namespace 'Root/WMI'.
.1364 17:22:35 (1) !! ERROR: (CheckWMIFeatures) : 0x80080005 - Server execution failed
.1365 17:22:35 (0) ** Collecting system information.
.1366 17:23:05 (1) !! ERROR: (CheckWMIInventory) : 0x80080005 - Server execution failed
.1367 17:23:05 (0) ** Verifying WMI providers loaded AFTER WMIDiag execution.
.1368 17:23:35 (1) !! ERROR: (CheckWMIStaticData) : 0x80080005 - Server execution failed
.1369 17:23:35 (0) ** Verifying WMI Repository files presence.
.1370 17:23:35 (1) !! ERROR: (CheckWMIRepositoryFiles) : 0x4C - Path not found. Folder 'C:\WINDOWS\SYSTEM32\WBEM\
.1371 17:23:35 (1) !! ERROR: Unable to access or find file 'INDEX.BTR'.
.1372 17:23:35 (1) !! ERROR: Unable to access or find file 'INDEX.MAP'.
.1373 17:23:35 (1) !! ERROR: Unable to access or find file 'MAPPING.VER'.
.1374 17:23:35 (1) !! ERROR: Unable to access or find file 'MAPPING1.MAP'.
.1375 17:23:35 (1) !! ERROR: Unable to access or find file 'MAPPING2.MAP'.
.1376 17:23:35 (1) !! ERROR: Unable to access or find file 'OBJECTS.DATA'.
.1377 17:23:35 (1) !! ERROR: Unable to access or find file 'OBJECTS.MAP'.
.1378 17:23:35 (0) ** WMIDiag v2.0 completed.
.
.
.
(Another report just like the one I posted previously was then produced. I won't copy it here again.)
It seems that these are big problems that just won't go away.
Do you have any other ideas, or are we looking at a Windows reinstall? (I would hate to do that, as I would have to reinstall all my installed applications.)
Thanks. I look forward to your response.
OK, let's try the "blow away the repository" technique one more time... then after the reboot, just let it churn for a while (5 minutes or so). Then launch the System Information utility (from Acessories, System Tools)... again, let it churn a while (so don't be concerned if it takes a long time... or errors out).
At the end you should end up with a consistent WMI repository.... it might be missing a bunch of stuff, but at least it should be consistent. I'd try the install of C# at this time, without any furthter WMIDiag work.
graye, OK, I did what you said: 1) Blew away the repository (like you instructed before); 2) Rebooted the computer, waiting over 5 minutes for the "churning" of the computer; and 3) Launched the System Information utility. But I got an error message from System Information utility:
Can't Collect Information
Cannot access the Windows Management Instrumentation software. Windows Management files may be moved or missing.
So I went into Windows Explorer to double-check the files in "C:\WINDOWS\system32\wbem"
So, what do I do now?
OK, graye, I've been trying to get around the complete reinstall for days now. I've attempted a number of "Repair Installs" of Windows, but no success yet. The OS still works, but that System Information Utility won't come up, and, of course, I can't install Visual C# Express, which I believe was the whole purpose of this thread, wasn't it?
Anyway, my next attempt will be to do as you said, a complete reinstall of Windows XP SP2. I'll report back here when that is complete. Thanks for hanging with me on this one.
graye, I tried and tried to get my OS to work, but no luck. I think you are absolutely correct, my OS is hosed.
Here is some further information on my OS. I bought it from Russia, at a special price, and thought I was saving money. Of course, it was a pirated copy, and the 25-digit Product Key never did authenticate with Microsoft. I think that is the real reason I had so many problems.
So, I'll just give up and buy a real, genuine copy of Windows XP Home, and install that. Then, I should be able to download Service Pack 2, and all the other updates, to Windows XP. Then, I should be able to download and install VIsual C# 2008 Express Edition, once and for all.
Thanks for helping me debug my current installation, and to finally realize that I can't get there from here, not with a pirated copy!
3 Ways to Join
Business Accounts
- Perfect for organizations
- Multiple users
- Save over 36%
- Create a Business Account
Answer for Membership
- Earn free access
- Showcase your knowledge
- No credit card required
- Sign Up to Answer
Loading Advertisement...
by: ororiolePosted on 2008-08-04 at 17:21:47ID: 22157275
Try installing 3.5 first, seperately.
http://www.microsoft.com/d
Make sure there are not any old 3.5 installs in control panel. Uninstall them if there are. REboot to clean machine. Install the framework. Reboot again. Now try your 2008 install.