locked
I have found an issue with MS13-098 which causes systems to be renamed to MINWINPC RRS feed

  • General discussion

  • I have found an issue with MS13-098 which causes systems to be renamed to  MINWINPC.  The issue has been reported in Japanese by Microsoft. The translation is:

    Phenomenon

      In Windows Server 2008 or Windows Vista, you might not be able to log an error appears to apply the new update the following programs, if you try to log on after the restart. •  MS12-024 (KB2653956)
    •  MS13-098 (KB2893294)


     Error message displayed is as follows.


     Incorrect password or user name


      Back to the top | feedback

    Collapse image  Cause

      This behavior occurs when you apply the update KB2653956 in the state of some data is damaged following registry key, or does not exist.

     HKEY_LOCAL_MACHINE \ SCHEMA \ wcm :/ / Microsoft-Windows-CoreOS? ...


     Any string will contain the part of the ... Note:.  Also, make sure to load the SystemRoot% \ system32 \ SMI \ Store \ Machine \ SCHEMA.DAT file% if the HKEY_LOCAL_MACHINE \ SCHEMA does not exist.

     When you apply the update of KB2653956 in the state where the registry key is not present, the value of the following registry is changed to MINWINPC, logon will not be able to.
    •  HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ActiveComputerName
    •  HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ComputerName

      Back to the top | feedback

    Collapse image  Solution

      If this occurs, change to the correct computer name the value of the ComputerName registry and ActiveComputerName start in safe mode, has been mentioned above, and then restart.
      Back to the top | feedback

    Collapse image  Workaround

      To prevent this phenomenon occurs, you download and run the System Update Readiness Tool from the following KB.

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

     By performing the system update Preparation tool registry that is described in Section Symptoms are repaired.
     If the repair is made, starting with log Recreated missing key as the following WinDir% \ Logs \ CBS \ CheckSUR.log file% is recorded.

     Recreated missing key:? Wcm :/ / Microsoft-Windows-CoreOS ... \ metadata \ elements \ ComputerName

     In addition, regardless of the presence or absence of entry damaged Microsoft-Windows-CoreOS, you can set the value of the ComputerName key in this tool.  For this reason, the following log is recorded in the CheckSUR.log.

     Recreated value: @ _type.
     Recreated value: @ dataOnly.
     Recreated value: @ default.
     Recreated value: @ description.
     Recreated value: @ displayName.
     Recreated value: @ handler.
     Recreated value: @ legacyName.
     Recreated value: @ legacyType.
     Recreated value: @ migrate.
     Recreated value: @ scope.
     Recreated value: @ xsd: type.

      Back to the top | feedback

     Note: This is a "FAST PUBLISH" article created directly from within the Microsoft support organization.  It contains information in response to emerging issues are listed.  As a result of the speed of information provided may be typographical errors are included in the article, you might be revised at any time without prior notice.  For other considerations, and use conditions

     Please refer to.
      Back to the top | feedback

    Collapse image  Property


      December 11, 2013 - Revision: - Last Review: 2901584: 4.0 Document Number

      This document that was written about products for.
    •  Windows Vista Business
    •  Windows Vista Business 64-bit edition
    •  Windows Vista Enterprise
    •  Windows Vista Enterprise 64-bit edition
    •  Windows Vista Home Basic
    •  Windows Vista Home Basic 64-bit edition
    •  Windows Vista Home Premium
    •  Windows Vista Home Premium 64-bit edition
    •  Windows Vista Starter
    •  Windows Vista Ultimate
    •  Windows Vista Ultimate 64-bit edition
    •  Windows Server 2008 Datacenter
    •  Windows Server 2008 Datacenter without Hyper-V
    •  Windows Server 2008 Enterprise
    •  Windows Server 2008 Enterprise without Hyper-V
    •  Windows Server 2008 for Itanium-Based Systems
    •  Windows Server 2008 Foundation
    •  Windows Server 2008 Standard
    •  Windows Server 2008 Standard without Hyper-V
    •  Windows Web Server 2008
    •  Windows HPC Server 2008
    •  Windows Essential Business Server 2008

    We are having the issue on hundreds of systems and I am rolling out the readiness tool mentioned above to prevent other systems from being affected.  In the mean time I have stopped deploying MS13-098 and am hoping Microsoft will go ahead and let all of their customers know about the problem instead of just one country.  Hopefully the original bulletin will be updated with this known issue.

    Wednesday, December 18, 2013 5:02 PM