none
How to access %Windir%\Panther\Setupact.log without desktop access

    Question

  • I have a Windows 7 Home Premium machine that I sysprep'd with an unattend.xml file I've previously used with Windows 7 Enterprise. After running sysprep and rebooting, I got the error:

    windows could not parse or process unattend answer file for pass specialize. the setting specified in the answer file cannot be applied. the error was detected while processing settings for component microsoft-windows-shell-setup

    I found this TechNet article: http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx, which says to check a couple of log files to see which line of the unattend file is a problem, but I can't get into Windows to access that log file and AFAIK, I can't read it from within the PE. Any other ideas?

    Thanks.

    • Edited by mhashemi Thursday, September 02, 2010 7:42 PM fixed error text formatting
    Thursday, September 02, 2010 7:39 PM

Answers

  • Hi,

    Although unattended installation fails, the installation should be able to keep going. You can finish the installation process and then open the log in the installed system.

    Another way is pressing Shift+F10 to open command prompt during installation. Then enter: Notepad. In Notepad, open the file C:\Windows\setupact.log.

    Please try to find clues in the log.

    Arthur Xie
    TechNet Subscriber Support in forum  
    If you have any feedback on our support, please contact tngfb@microsoft.com.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by mhashemi Wednesday, September 08, 2010 8:13 PM
    Friday, September 03, 2010 8:40 AM
    Moderator

All replies

  • I wouldn't use a unattend.xml for another version than it was created for. If you create a file in WSIM it loads the corresponding WIM image of the operating system you are creating it for. Instead of looking for the logs i would suggest you quickly recreate the unattend.xml for you Home Premium version.

    What probably happened is that the xml file you are now using is configuring an enterprise feature during the specialize pass which Home Premium doesn't have.

    Thursday, September 02, 2010 9:11 PM
  • I should have posted my unattend file too. Maybe it doesn't like the "cpi:offlineImage" value of "catalog:d:/sources/install_windows 7 enterprisen.cl". See anything specific that needs changing? Thanks.

     

    <?xml version="1.0" encoding="utf-8"?>

    <unattend xmlns="urn:schemas-microsoft-com:unattend">

        <settings pass="specialize">

            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <Display>

                    <ColorDepth>24</ColorDepth>

                    <HorizontalResolution>1024</HorizontalResolution>

                    <RefreshRate>75</RefreshRate>

                    <VerticalResolution>768</VerticalResolution>

                </Display>

                <TaskbarLinks>

                    <Link0>C:\Program Files\Windows AIK\Tools\amd64\imagex.exe</Link0>

                </TaskbarLinks>

                <WindowsFeatures>

                    <ShowWindowsMail>false</ShowWindowsMail>

                </WindowsFeatures>

                <ComputerName>*</ComputerName>

                <CopyProfile>true</CopyProfile>

                <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>

                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>

                <ProductKey>enterpriseProductKey</ProductKey>

                <ShowWindowsLive>false</ShowWindowsLive>

                <TimeZone>Mountain Standard Time</TimeZone>

            </component>

            <component name="Security-Malware-Windows-Defender" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <DisableAntiSpyware>true</DisableAntiSpyware>

            </component>

            <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <RunSynchronous>

                    <RunSynchronousCommand wcm:action="add">

                        <Order>1</Order>

                        <Path>net user administrator /active:yes</Path>

                    </RunSynchronousCommand>

                </RunSynchronous>

            </component>

            <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <SkipAutoActivation>true</SkipAutoActivation>

            </component>

        </settings>

        <settings pass="oobeSystem">

            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <InputLocale>en-us</InputLocale>

                <SystemLocale>en-us</SystemLocale>

                <UILanguage>en-us</UILanguage>

                <UserLocale>en-us</UserLocale>

            </component>

            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

                <FirstLogonCommands>

                    <SynchronousCommand wcm:action="add">

                        <CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk enterpriseProductKey</CommandLine>

                        <Order>1</Order>

                        <RequiresUserInput>false</RequiresUserInput>

                    </SynchronousCommand>

                    <SynchronousCommand wcm:action="add">

                        <CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>

                        <Order>2</Order>

                        <RequiresUserInput>false</RequiresUserInput>

                    </SynchronousCommand>

    <SynchronousCommand wcm:action="add">

                        <CommandLine>call \\server\share\start.bat</CommandLine>

                        <Order>3</Order>

                        <RequiresUserInput>false</RequiresUserInput>

                    </SynchronousCommand>

    <SynchronousCommand wcm:action="add">

                        <CommandLine>c:\admin\taskbar.bat</CommandLine>

                        <Order>4</Order>

                        <RequiresUserInput>false</RequiresUserInput>

                    </SynchronousCommand>

                </FirstLogonCommands>

                <OOBE>

                    <HideEULAPage>true</HideEULAPage>

                    <NetworkLocation>Work</NetworkLocation>

                    <ProtectYourPC>3</ProtectYourPC>

                </OOBE>

                <UserAccounts>

                    <AdministratorPassword>

                        <Value>someLongValue</Value>

                        <PlainText>false</PlainText>

                    </AdministratorPassword>

                </UserAccounts>

            </component>

        </settings>

        <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows 7 enterprisen.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

    </unattend>


    Thursday, September 02, 2010 9:16 PM
  • Is the Home Premium also a 64-bit OS?

     

    Also this line might cause a problem, it is looking for the Enterpise clg

    <cpi:offlineImage cpi:source="catalog:d:/sources/install_windows 7 enterprisen.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

     

    i would try to create a new xlm file for the home premium installation

    Thursday, September 02, 2010 9:18 PM
  • Hi,

    Although unattended installation fails, the installation should be able to keep going. You can finish the installation process and then open the log in the installed system.

    Another way is pressing Shift+F10 to open command prompt during installation. Then enter: Notepad. In Notepad, open the file C:\Windows\setupact.log.

    Please try to find clues in the log.

    Arthur Xie
    TechNet Subscriber Support in forum  
    If you have any feedback on our support, please contact tngfb@microsoft.com.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by mhashemi Wednesday, September 08, 2010 8:13 PM
    Friday, September 03, 2010 8:40 AM
    Moderator
  • Hi,

    Just want to check how things are going. Have you found the root cause from the log?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Wednesday, September 08, 2010 6:54 AM
    Moderator
  • I ended up changing the "<cpi:offlineImage cpi:source="catalog:d:/sources/install_windows 7 enterprisen.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />" line.
    Wednesday, September 08, 2010 8:14 PM