/build/static/layout/Breadcrumb_cap_w.png
04/03/2019 133 views

Hi Everybody,


Today, i have the same error : "'fs1:\EFI\Microsoft\Boot\bootmgfw.efi' is not recognized...."


I am using "Script Installation" on HP Prodesk 400 G4 SFF with a official Microsoft Win 10 1809 x64  Iso and "Create UEFI partitions" Task. 


Os Installation task seems OK but after Drivers Copy Task, the computer reboot but he can't boot on OS with "UEFI Interactive Shell V2.1" and  "'fs1:\EFI\Microsoft\Boot\bootmgfw.efi' is not recognized...." error....


have you an idea? 


Thank's for your help.


Best regards. 

0 Comments   [ + ] Show comments

Comments


All Answers

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0

I only do images and just looked at the one scripted install I have and it does not have a check box to run the driver feed so that most likely is the problem, you don't have the proper drivers.

You may have to create a mid level task to call the driver feed

Mine is located in a different numbered directory then what you will have.  I use custom deployments so I need to manually call the driver feed.

Create a mid level bat task: (you will have to look at your kbox and determine the directory number)

Y:\applications\711\copy_drivers.vbs

Answered 04/03/2019 by: SMal.tmcc
Red Belt

  • Thanks you very much for you answer,

    after lot of tests, i am seeing that the problem are coming to "System Installation Task", Windows Os is not installed on Disk when the task is executed.

    Drivers is OK, ISO source is OK ans unattend.xml is ok too.

    Now I'm going around the problem with a "Bat Script" where i execute the setup.exe (Y:\Source_cds\) manually with copy of unattend.xml on T:\ and it's work... but i know that isn't a good solution
0

do you have the proper pretasks?


Answered 04/03/2019 by: SMal.tmcc
Red Belt

  • yes, but... same issues....
    • can you share the xml
    • what version is your kbox?
      • you need 6.1 for 1809 support and also need to create a new kbe after upgrade
  • Kbox is full updates: 6.1.251

    And unattend.xml :

    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <UseConfigurationSet>true</UseConfigurationSet>
    <UserData>
    <AcceptEula>true</AcceptEula>
    <FullName>Admin Win10 V0.1</FullName>
    <Organization>My Orga</Organization>
    <ProductKey>
    <Key>W269N-WFGWX-YVC9B-4J6C9-T83GX</Key>
    <WillShowUI>OnError</WillShowUI>
    </ProductKey>
    </UserData>
    <ImageInstall>
    <OSImage>
    <InstallToAvailablePartition>true</InstallToAvailablePartition>
    </OSImage>
    </ImageInstall>
    </component>
    <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <UILanguage>fr-fr</UILanguage>
    <SetupUILanguage>
    <UILanguage>fr-fr</UILanguage>
    </SetupUILanguage>
    <InputLocale>fr-fr</InputLocale>
    <SystemLocale>fr-fr</SystemLocale>
    <UserLocale>fr-fr</UserLocale>
    </component>
    </settings>
    <settings pass="specialize">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <RegisteredOwner>Admin Win10 V0.1</RegisteredOwner>
    <RegisteredOrganization>My orga</RegisteredOrganization>
    <ProductKey>W269N-WFGWX-YVC9B-4J6C9-T83GX</ProductKey>
    <TimeZone>Romance Standard Time</TimeZone>
    <AutoLogon>
    <Enabled>true</Enabled>
    <Username>myadmin</Username>
    <Password>
    <PlainText>true</PlainText>
    <Value>1P@asswordTest!</Value>
    </Password>
    <LogonCount>1</LogonCount>
    </AutoLogon>
    <ComputerName>*</ComputerName>
    </component>
    <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <Identification>
    <JoinWorkgroup>WORKGROUP</JoinWorkgroup>
    </Identification>
    </component>
    <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <RunSynchronous>
    <RunSynchronousCommand wcm:action="add">
    <Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>
    <Description>Setting Network Location</Description>
    <Order>1</Order>
    <WillReboot>OnRequest</WillReboot>
    </RunSynchronousCommand>
    </RunSynchronous>
    </component>
    </settings>
    <settings pass="oobeSystem">
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <OOBE>
    <HideEULAPage>true</HideEULAPage>
    <SkipMachineOOBE>false</SkipMachineOOBE>
    <SkipUserOOBE>false</SkipUserOOBE>
    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
    <ProtectYourPC>3</ProtectYourPC>
    </OOBE>
    <UserAccounts>
    <LocalAccounts>
    <LocalAccount wcm:action="add">
    <Name>myadmin</Name>
    <Group>Administrators</Group>
    <Password>
    <Value>1P@asswordTest!</Value>
    <PlainText>true</PlainText>
    </Password>
    </LocalAccount>
    </LocalAccounts>
    </UserAccounts>
    </component>
    <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
    <InputLocale>fr-fr</InputLocale>
    <SystemLocale>fr-fr</SystemLocale>
    <UILanguage>fr-fr</UILanguage>
    <UserLocale>fr-fr</UserLocale>
    </component>
    </settings>
    </unattend>


    What do you think?
    • when Installation OS task as running, the error said that OS sources isn't accessible...
      • is it only this model of computer doing this?
      • No. EveryModels and EveryOS...

        Yesterday, i was finding the problem but now i have not a solution.

        When "Os Installation Task" are running, setup.exe chrash with Fatal error ( install.wim don't exist):

        2019-04-04 15:09:18, Info SetOSImageInfoOnBB: Windows image file location is [install.wim]
        2019-04-04 15:09:18, Error [0x06066f] IBS CollectInformationForImage: Could not find image file [install.wim] specified for 'ImageInfo\OSImage'.[gle=0x000004cf]
        2019-04-04 15:09:18, Error [0x000671] SetOSImageInfoOnBB: (hr = 0x80070002) Could not cache the Windows image XML info [install.wim][gle=0x000004cf]
        2019-04-04 15:09:18, Error [0x00054b] Callback_SetWinPEAndOSImageInfoOnBB: (hr = 0x80070002) Failed to collect WinPE and Windows image XML info.[gle=0x000004cf]
        2019-04-04 15:09:18, Info IBSLIB PublishCriticalError: Publishing critical error message [Windows n’a pas pu collecter d’informations pour [OSImage] car le fichier image spécifié [install.wim] n’existe pas.]
        2019-04-04 15:09:18, Warning [0x0a011f] UI SpwLoadBitmap failed: Bitmap Id [408], Error code 0.
        2019-04-04 15:09:18, Warning [0x0a011f] UI SpwLoadBitmap failed: Bitmap Id [416], Error code 126.
        2019-04-04 15:09:18, FatalError bResult[gle=0x0000007e]
        2019-04-04 15:09:18, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFCCAAC997D in Y:\source_cds\31\Sources\SPWIZENG.DLL (+000000000001997D). Minidump attached (82898 bytes) to diagerr.xml and X:\windows\panther\mnd8DFE.diagerr.mdmp.


        But, with command prompt, i can see Install.wim on Y:\Source_cds\31\sources\ .... And more, i can run setup.exe successfully.

        i am thinking that is a k2000 access rights bug...
    • is not a k2000 access rights bug... with a new K2000 Vm, i have the same problem...

      I don't understand....
      • it could be an access problem. Have you changed your samba share password lately?
        When you change that you must compile new KBE's. that password is put into the KBE. And that password is used on RSA's also. If you have not I would try resetting the password and create a new KBE
      • I had not update my samba share password. But, i was testing update password and regenerate KBE annnnnnnd....... same problem... :(

        "Google" say maybe a Corrupted ISO , but i was trying with lot of Windows 10 versions...

        am i alone with this error??? XD

        Thanks for your help.
      • Hi SMal.tmcc,

        All the problems come from the MVLS license number... It isn't recognized by setup.exe to automatically choose windows version and it was crashing.

        So, Microsoft advises to use a generic licence number when a Automatic deployment are used:
        https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

        Since i reconfigured the licence number in deployment task, it's work!

        Thanks you very much for your help.

        Best regards.

        Martin.
      • good to know