Windows 10 1909 Installation "Antwortdatei nicht gefunden"

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 27 Dez 2019, 11:02

Hallo zusammen,

und zwar stehe ich aktuell vor der herausvorderung das ich eine Netboot install für windows 1909 fertig gemacht habe die aber nicht funktioniert da dann nach dem 1. neustart nach dem kopieren beim "Start Setup" die fehlermeldung bekommen "Interner Fehler .. Antwortdatei Datei nicht gefunden".

Ich habe das ganze wie in der Anleitung beschrieben durchgeführt.

Komischerweise ist mir im Log unter "Bootimage" aufgefallen das der die Version "Windows 10 1607 Ultimate Edition" wählt obwohl es "Windows 10 1909 Pro N Edition" sein sollte und er zeigt mir falsche werte an wie z.b. "Falsche Mac".

Code: Alles auswählen

(9712)    [1] [Dec 27 10:23:07:872] ============ Version 4.12.3.0 script "c:\opsi\setup.opsiscript"
(9713)    [1] [Dec 27 10:23:07:872]              used script encoding: cp1252
(9714)    [1] [Dec 27 10:23:07:872]              used system encoding: cp1252
(9715)    [1] [Dec 27 10:23:07:872]              start: 2019-12-27  10:23:07
(9716)    [1] [Dec 27 10:23:07:872]              on client named    "MINWINPC"
(9717)    [1] [Dec 27 10:23:07:872]              loggedin user    ""
(9718)    [1] [Dec 27 10:23:07:887]              opsi-script running as    "MINWINPC$"
(9720)    [1] [Dec 27 10:23:07:887]              opsi-script running in standard script mode
(9721)    [1] [Dec 27 10:23:07:887] executing: "c:\opsi\opsi-script\files64\opsi-winst\winst64.exe"
(9722)    [1] [Dec 27 10:23:07:887] system infos:
(9724)    [1] [Dec 27 10:23:07:887] 94-65-74-F7-1E-B3  -  PC hardware address
(9725)    [1] [Dec 27 10:23:07:887]   -  IP name
(9726)    [1] [Dec 27 10:23:07:887]   -  IP address
(9727)    [1] [Dec 27 10:23:07:887] ENU  -  System default locale
(9733)    [1] [Dec 27 10:23:07:887] MS Windows 10.0 64 Bit, Release: 1607, Edition: Ultimate Edition"


Hier sind meine Installierten Pakete

Code: Alles auswählen

Product ID                Version                   Name
   ========================================================================================================================================================================================================================================
   activate-win              1.0-9                     Windows Activation
   config-win-base           4.0.1-1                   Windows Customizing
   config-win10              4.1.1-8                   Configure Windows 10
   debian9                   4.1.0.2-6                 Linux Debian 9
   hwaudit                   4.1.0.8-1                 Client Hardwareinventarisierung
   hwinvent                  4.1.0.1-1                 Hardware Inventarisierung
   javavm                    1.8.0.101or1.8.0.102-1    Oracle Java Runtime Environment                                                                                                                                                     
   l-debuntu-upgrade         4.1.0.0-5                 Debian / Ubuntu (LTS) upgrade Product                                                                                                                                               
   l-desktop                 4.1.0.5-5                 Desktop for Linux                                                                                                                                                                   
   l-hwaudit                 4.1.0.1-3                 Linux Client Hardwareinventory                                                                                                                                                     
   l-opsi-server             4.1.1.14-3                Installs opsi                                                                                                                                                                       
   l-opsi-server-migrate     4.1.2-2                   Installs opsi 4.1 from 4.0                                                                                                                                                         
   l-os-postinst             4.0.5.1-4                 Linux post bootimage install                                                                                                                                                       
   l-ssh-root-login          1.0-3                     l-ssh-root-login                                                                                                                                                                   
   l-system-update           4.0.7.1-6                 Linux System Update                                                                                                                                                                 
   l-virtualbox              5.1-1                     l-virtualbox                                                                                                                                                                       
   memtest86                 5.01-2                    Memtest86+                                                                                                                                                                         
   opsi-client-agent         4.1.0.0-32                opsi.org client agent                                                                                                                                                               
   opsi-clonezilla           4.1.0.1-2                 Clonezilla over opsi                                                                                                                                                               
   opsi-configed             4.1.4.3.3-2               opsi configed                                                                                                                                                                       
   opsi-linux-client-agent   4.1.0.19-11               opsi.org client agent for Linux                                                                                                                                                     
   opsi-logviewer            3.1-7                     opsi logfile viewer                                                                                                                                                                 
   opsi-script-test          4.12.1.5-1                opsi-script test                                                                                                                                                                   
   opsi-setup-detector       4.1.0.14-1                opsi-setup-detector                                                                                                                                                                 
   opsi-template             4.0.6-1                   opsi template product                                                                                                                                                               
   opsi-template-with-admin  4.1.0.0-2                 opsi template for installs with logged in admin                                                                                                                                     
   opsi-uefi-netboot         4.0.5-3                   opsi-uefi-netboot                                                                                                                                                                   
   opsi-wan-config-off       4.0.1-1                   opsi-wan-config-off                                                                                                                                                                 
   opsi-wan-config-on        4.0.1-1                   opsi-wan-config-off                                                                                                                                                                 
   opsi-wim-capture          4.1.0.1-7                 opsi-wim-capture                                                                                                                                                                   
   opsi-wim-delete           4.1.0.1-1                 opsi-wim-delete                                                                                                                                                                     
   opsi-wim-info             4.0.7.2-1                 opsi-wim-info                                                                                                                                                                       
   opsi-winpe                4.1.0-1                   WinPE patching tool                                                                                                                                                                 
   opsi-winst                4.12.3.1-1                winst                                                                                                                                                                               
   shutdownwanted            1.0-6                     shutdown wanted
   swaudit                   4.1.0.0-3                 Client Software inventory (Windows / Linux)
   win10-x64                 4.1.0.1-12                Windows 10 x64
   win10_1909                4.1.0.1-9                 Windows 10 x64
   win7-x64                  4.1.0.1-9                 Windows 7 - x64
   win7_firewall_off         1.0-1                     win7_firewall_off
   windomain                 1.0-11                    Join NT/AD Domain
   windows10-upgrade         19.09-7                   Windows 10 Upgrade
   windows_10_crl            1.0-1                     windows_10_crl
   windows_notfallpatch      1.0-1                     windows_notfallpatch
   wipedisk                  1.1-1                     Festplatte oder Partitionen loeschen




Ich habe auch bereits die neuste "Opsi-linux-Bootimage" version installiert und sowohl auch die neusten "win10-x64" aus Experimental installiert und dennoch kriege ich diese Fehlermeldung.

Habt ihr vllt. noch eine Idee was ich falsch machen könnte?

Mfg

Benutzeravatar
ThomasT
uib-Team
Beiträge: 226
Registriert: 26 Jun 2013, 12:26

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon ThomasT » 02 Jan 2020, 09:42

Ich habe das ganze wie in der Anleitung beschrieben durchgeführt.

Was genau hast du denn gemacht?

Zur Version: Das ist die von dir verwendete WinPE Version. Lade dir doch mal bei gelegenheit das neueste Win10 ADK runter....
Zur Fehlermeldung: Hast du eine unattend.xml unter

Code: Alles auswählen

/var/lib/opsi/depot/win10-x64/custom
Kein Support per DM!
_________________________
opsi support - https://www.uib.de/
For productive opsi installations we recommend support contracts.

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 02 Jan 2020, 12:23

Hallo

Also ich habe das ganze wie in der Anleitung installiert.
Windows 10 neu installiert Windows 10 ADK installiert mit dem Bereitstellung Tool dann opsi Client Agent installiert und dann den Opsi Winpe ausführen lassen. Habe dann den Inhalt von winpe Media ins opsi Paket Winpe kopiert und die ISO nach installfiles kopiert. Danach opsi-set-rights gemacht damit die Berechtigung gesetzt wird.

Jaa ich habe auch eine unattended XML File liegen.

Das komische ist das er auch die falsch MAC, Hostname, IP Adresse alles falsch.

Ich habe auch im Log Bootimage auf Loglevel 7 gestellt und sehe auch das der vorher alles richtig ausliest nur die bei dem Part wo das eigentlich richtig sein soll.

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 06 Jan 2020, 10:43

Also,

ich habe jetzt nochmal ein neues "win10-x64" von opsi installiert sowohl eine neue "Windows 10 1909" VM fertig gemacht und "Windows 10 ADK 1903" und das dazugehörige Addon "Win PE" installert und dann über opsi das "Opsi Winpe" Paket installiert und dann den Inhalt von media in den jeweiligen Ordner geschoben sowie den Inhalt von der "Windows ISO" in installfiles kopiert und im Anschluss "opsi-set-rights" gemacht.

Leider kriege ich weiterhin nachdem von Windows "Start Setup" kommt direkt die Meldung "Interner Fehler beim Laden oder Suchen einer Antwortdatei für die unbeaufsichtigte Installation" und mehr passiert nichts.

Hier noch einmal der Log von "Bootimage"

Code: Alles auswählen

(0)       Jan 06 10:27:03 [opsiinit] opsi init script started
(1)       Jan 06 10:27:03 [opsiinit] opsi linux bootimage version: 20191114 (4.1)
(2)       Jan 06 10:27:13 [opsiinit] getBootParam(pwh): cmdline: initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=kikxxl.corp product=win10-x64 hn=jean-w10 pckey=*** confidential *** service=https://192.168.1.16:4447/rpc BOOT_IMAGE=install-x64
(3)       Jan 06 10:27:13 [opsiinit] boot param pwh=
(4)       Jan 06 10:27:13 [opsiinit] getBootParam(nodhcp): cmdline: initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=kikxxl.corp product=win10-x64 hn=jean-w10 pckey=*** confidential *** service=https://192.168.1.16:4447/rpc BOOT_IMAGE=install-x64
(5)       Jan 06 10:27:13 [opsiinit] boot param nodhcp=0
(6)       Jan 06 10:27:13 [opsiinit] getBootParam(hn): cmdline: initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=kikxxl.corp product=win10-x64 hn=jean-w10 pckey=*** confidential *** service=https://192.168.1.16:4447/rpc BOOT_IMAGE=install-x64
(7)       Jan 06 10:27:13 [opsiinit] boot param hn=jean-w10
(8)       Jan 06 10:27:13 [opsiinit] getBootParam(dhclienttimeout): cmdline: initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=kikxxl.corp product=win10-x64 hn=jean-w10 pckey=*** confidential *** service=https://192.168.1.16:4447/rpc BOOT_IMAGE=install-x64
(9)       Jan 06 10:27:13 [opsiinit] getBootParam(lang): cmdline: initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 dn=kikxxl.corp product=win10-x64 hn=jean-w10 pckey=*** confidential *** service=https://192.168.1.16:4447/rpc BOOT_IMAGE=install-x64
(10)      Jan 06 10:27:13 [opsiinit] boot param lang=
(11)      Jan 06 10:27:13 [opsiinit] loading keymap de-latin1-nodeadkeys
(12)      Jan 06 10:27:13 [opsiinit] setting language environment (LANG=de_DE.UTF8, LANGUAGE=de, LC_ALL=de_DE.UTF8)
(13)      Jan 06 10:27:13 [opsiinit] getNetworkDevices(): link forced
(14)      Jan 06 10:27:13 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(15)      Jan 06 10:27:13 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(16)      Jan 06 10:27:13 [opsiinit] no devices found, sleeping 3 seconds
(17)      Jan 06 10:27:16 [opsiinit] getNetworkDevices(): link forced
(18)      Jan 06 10:27:16 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(19)      Jan 06 10:27:16 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(20)      Jan 06 10:27:16 [opsiinit] no devices found, sleeping 3 seconds
(21)      Jan 06 10:27:19 [opsiinit] getNetworkDevices(): link forced
(22)      Jan 06 10:27:19 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(23)      Jan 06 10:27:19 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(24)      Jan 06 10:27:19 [opsiinit] no devices found, sleeping 3 seconds
(25)      Jan 06 10:27:22 [opsiinit] getNetworkDevices(): link forced
(26)      Jan 06 10:27:22 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(27)      Jan 06 10:27:22 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(28)      Jan 06 10:27:22 [opsiinit] no devices found, sleeping 3 seconds
(29)      Jan 06 10:27:25 [opsiinit] getNetworkDevices(): link forced
(30)      Jan 06 10:27:25 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(31)      Jan 06 10:27:25 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(32)      Jan 06 10:27:25 [opsiinit] no devices found, sleeping 3 seconds
(33)      Jan 06 10:27:28 [opsiinit] getNetworkDevices(): link forced
(34)      Jan 06 10:27:28 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(35)      Jan 06 10:27:28 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(36)      Jan 06 10:27:28 [opsiinit] no devices found, sleeping 3 seconds
(37)      Jan 06 10:27:31 [opsiinit] getNetworkDevices(): link forced
(38)      Jan 06 10:27:31 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(39)      Jan 06 10:27:31 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(40)      Jan 06 10:27:31 [opsiinit] no devices found, sleeping 3 seconds
(41)      Jan 06 10:27:34 [opsiinit] getNetworkDevices(): link forced
(42)      Jan 06 10:27:34 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(43)      Jan 06 10:27:34 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(44)      Jan 06 10:27:34 [opsiinit] no devices found, sleeping 3 seconds
(45)      Jan 06 10:27:37 [opsiinit] getNetworkDevices(): link forced
(46)      Jan 06 10:27:37 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(47)      Jan 06 10:27:37 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(48)      Jan 06 10:27:37 [opsiinit] no devices found, sleeping 3 seconds
(49)      Jan 06 10:27:41 [opsiinit] getNetworkDevices(): link forced
(50)      Jan 06 10:27:41 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(51)      Jan 06 10:27:41 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(52)      Jan 06 10:27:41 [opsiinit] no devices found, sleeping 3 seconds
(53)      Jan 06 10:27:44 [opsiinit] getNetworkDevices(): link forced
(54)      Jan 06 10:27:44 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(55)      Jan 06 10:27:44 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(56)      Jan 06 10:27:44 [opsiinit] no devices found, sleeping 3 seconds
(57)      Jan 06 10:27:47 [opsiinit] getNetworkDevices(): link forced
(58)      Jan 06 10:27:47 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(59)      Jan 06 10:27:47 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(60)      Jan 06 10:27:47 [opsiinit] no devices found, sleeping 3 seconds
(61)      Jan 06 10:27:50 [opsiinit] getNetworkDevices(): link forced
(62)      Jan 06 10:27:50 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(63)      Jan 06 10:27:50 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(64)      Jan 06 10:27:50 [opsiinit] no devices found, sleeping 3 seconds
(65)      Jan 06 10:27:53 [opsiinit] getNetworkDevices(): link forced
(66)      Jan 06 10:27:53 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(67)      Jan 06 10:27:53 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(68)      Jan 06 10:27:53 [opsiinit] no devices found, sleeping 3 seconds
(69)      Jan 06 10:27:56 [opsiinit] getNetworkDevices(): link forced
(70)      Jan 06 10:27:56 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(71)      Jan 06 10:27:56 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(72)      Jan 06 10:27:56 [opsiinit] no devices found, sleeping 3 seconds
(73)      Jan 06 10:27:59 [opsiinit] getNetworkDevices(): link forced
(74)      Jan 06 10:27:59 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(75)      Jan 06 10:27:59 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(76)      Jan 06 10:27:59 [opsiinit] no devices found, sleeping 3 seconds
(77)      Jan 06 10:28:02 [opsiinit] getNetworkDevices(): link forced
(78)      Jan 06 10:28:02 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(79)      Jan 06 10:28:02 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(80)      Jan 06 10:28:02 [opsiinit] no devices found, sleeping 3 seconds
(81)      Jan 06 10:28:05 [opsiinit] getNetworkDevices(): link forced
(82)      Jan 06 10:28:05 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(83)      Jan 06 10:28:05 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(84)      Jan 06 10:28:05 [opsiinit] no devices found, sleeping 3 seconds
(85)      Jan 06 10:28:08 [opsiinit] getNetworkDevices(): link forced
(86)      Jan 06 10:28:08 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(87)      Jan 06 10:28:08 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(88)      Jan 06 10:28:08 [opsiinit] no devices found, sleeping 3 seconds
(89)      Jan 06 10:28:11 [opsiinit] getNetworkDevices(): link forced
(90)      Jan 06 10:28:11 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(91)      Jan 06 10:28:11 [opsiinit] getNetworkDevices(): no devices with link found, returning error
(92)      Jan 06 10:28:11 [opsiinit] no devices found, sleeping 3 seconds
(93)      Jan 06 10:28:14 [opsiinit] getNetworkDevices(): device(s) found:  enp0s3, device(s) with link:
(94)      Jan 06 10:28:14 [opsiinit] getNetworkDevices(): no devices with link found, returning  enp0s3
(95)      Jan 06 10:28:14 [opsiinit] using dhcp, adding entry for device enp0s3 to /etc/netplan/01-enp0s3.yaml
(96)      Jan 06 10:28:14 [opsiinit] Setting hostname to jean-w10 as supplied by cmdline
(97)      Jan 06 10:28:14 [opsiinit] opsi init script ended
(99)      [6] [Jan 06 10:28:20] Executing: echo 0 > /proc/sys/kernel/printk (Posix.py|856)
(100)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(102)     [6] [Jan 06 10:28:20] Executing: setterm -msg off -blank 0 -powersave off < /dev/tty6 > /dev/tty6 (Posix.py|856)
(103)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(105)     [6] [Jan 06 10:28:20] Executing: dmesg (Posix.py|856)
(106)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(528)     [6] [Jan 06 10:28:20] Executing: lsmod (Posix.py|856)
(529)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(545)     [6] [Jan 06 10:28:20] Executing: cat /etc/environment (Posix.py|856)
(546)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(551)     [6] [Jan 06 10:28:20] Executing: env 2>&1 (Posix.py|856)
(552)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(563)     [6] [Jan 06 10:28:20] Executing: locale 2>&1 (Posix.py|856)
(564)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(581)     [6] [Jan 06 10:28:20] Executing: swapoff -a (Posix.py|856)
(582)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(584)     [6] [Jan 06 10:28:20] Found ethernet device: 'enp0s3' (Posix.py|406)
(586)     [6] [Jan 06 10:28:20] Executing: /sbin/ifconfig enp0s3 up (Posix.py|856)
(587)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(589)     [6] [Jan 06 10:28:20] Executing: mii-tool enp0s3 (Posix.py|856)
(590)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(593)     [6] [Jan 06 10:28:20] Executing: ethtool enp0s3 (Posix.py|856)
(594)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(622)     [5] [Jan 06 10:28:20] Detected link on device 'enp0s3' (master.py|731)
(623)     [5] [Jan 06 10:28:20] No file dhclient.enp0s3.leases found (master.py|764)
(624)     [5] [Jan 06 10:28:20] Waiting for network devices to get configured by dhcp (master.py|810)
(625)     [6] [Jan 06 10:28:20] Executing: /sbin/ifconfig enp0s3 (Posix.py|856)
(626)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(638)     [6] [Jan 06 10:28:20] Executing: /sbin/ip route (Posix.py|856)
(639)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(643)     [5] [Jan 06 10:28:20] All network devices configured (master.py|823)
(644)     [5] [Jan 06 10:28:20] leases: enp0s3:/var/lib/dhcp/dhclient.leases (master.py|848)
(645)     [5] [Jan 06 10:28:20] Getting dhcp result for device: enp0s3 (master.py|852)
(646)     [6] [Jan 06 10:28:20] Executing: /sbin/ifconfig enp0s3 (Posix.py|856)
(647)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(658)     [6] [Jan 06 10:28:20] Executing: /sbin/ip route (Posix.py|856)
(659)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(663)     [6] [Jan 06 10:28:20] Current network config: (master.py|885)
(664)     [6] [Jan 06 10:28:20]    device          : enp0s3 (master.py|886)
(665)     [6] [Jan 06 10:28:20]    hardwareAddress : fe:00:00:16:09:99 (master.py|887)
(666)     [6] [Jan 06 10:28:20]    ipaddress       : 192.168.199.121 (master.py|888)
(667)     [6] [Jan 06 10:28:20]    netmask         : 255.255.255.0 (master.py|889)
(668)     [6] [Jan 06 10:28:20]    gateway         : 192.168.199.1 (master.py|890)
(669)     [6] [Jan 06 10:28:20]    nameserver      : 192.168.0.167 (master.py|891)
(670)     [6] [Jan 06 10:28:20]    hostname        : jean-w10 (master.py|892)
(671)     [6] [Jan 06 10:28:20]    domain          : kikxxl.corp (master.py|893)
(672)     [6] [Jan 06 10:28:20]    nextserver      : https://192.168.1.16:4447/rpc (master.py|894)
(673)     [5] [Jan 06 10:28:20] try to load efivars module: modprobe efivars (master.py|602)
(674)     [6] [Jan 06 10:28:20] Executing: /sbin/modprobe efivars (Posix.py|856)
(675)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(678)     [5] [Jan 06 10:28:20] we are not running in uefi mode (master.py|606)
(679)     [6] [Jan 06 10:28:20] Found ethernet device: 'enp0s3' (Posix.py|406)
(680)     [6] [Jan 06 10:28:20] Executing: /sbin/ifconfig enp0s3 (Posix.py|856)
(681)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(692)     [6] [Jan 06 10:28:20] Executing: /sbin/ip route (Posix.py|856)
(693)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(697)     [6] [Jan 06 10:28:20] Default network interface found: enp0s3 (Posix.py|501)
(698)     [6] [Jan 06 10:28:20] Executing: /sbin/ifconfig enp0s3 (Posix.py|856)
(699)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(710)     [6] [Jan 06 10:28:20] Executing: /sbin/ip route (Posix.py|856)
(711)     [6] [Jan 06 10:28:20] Using encoding 'UTF-8' (Posix.py|889)
(715)     [6] [Jan 06 10:28:20] Using FQDN 'jean-w10.kikxxl.corp' (master.py|1234)
(716)     [6] [Jan 06 10:28:20] Creating JSONRPCBackend instance (try #0) (master.py|1273)
(723)     [6] [Jan 06 10:28:21] <JSONRPCBackend(host=u'192.168.1.16', compression=False)>: Connected to service (JSONRPC.py|515)
(730)     [5] [Jan 06 10:28:21] Product-id is 'win10-x64' (master.py|1389)
(743)     [5] [Jan 06 10:28:21] Fetching product properties... (master.py|1419)
(756)     [5] [Jan 06 10:28:21] Fetching config states... (master.py|1428)
(769)     [5] [Jan 06 10:28:22] Requesting product license... (master.py|1438)
(770)     [5] [Jan 06 10:28:22] Using license management to get licensekey (master.py|1440)
(777)     [6] [Jan 06 10:28:22] Product license key: MH37W-N47XK-V7XM9-C7227-GCQG9


und hier nochmal die "win10-x64/custom/unattend.xml"

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
        ====================
        WINDOWSPE SETTINGS
        ====================
        The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
        For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
        -->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>#@diskindex*#</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        #@modify_partitions*#
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>#@productkey*#</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>#@fullname*#</FullName>
                <Organization>#@orgname*#</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>#@imagename*#</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>#@installdiskindex*#</DiskID>
                        <PartitionID>#@windows_partition_number*#</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>#@winpe_uilanguage*#</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>#@winpe_inputlocale*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@winpe_uilanguage*#</UILanguage>
            <UILanguageFallback>#@winpe_uilanguage_fallback*#</UILanguageFallback>
            <UserLocale>#@winpe_uilanguage*#</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
        =====================
        GENERALIZE SETTINGS
        =====================
        The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
        A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
        In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
        When a system is generalized, specific configuration data for a given installation of Windows is removed.
        For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
        The generalize configuration pass runs only when you use the sysprep /generalize command.
        Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
        -->
    <!--
        <settings pass="generalize">
        </settings>
        -->
    <!--
        =====================
        SPECIALIZE SETTINGS
        =====================
        During the specialize pass of Windows Setup, machine-specific information for the image is applied.
        For example, you can configure network settings, international settings, and domain information.
        The specialize pass is used in conjunction with the generalize pass.
        The generalize pass is used to create a Windows reference image that can be used throughout an organization.
        From this basic Windows reference image, you can add further customizations that apply to different divisions
        within an organization or apply to different installations of Windows.
        The specialize pass is used to apply these specific customizations.
        -->
    <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">
            <ComputerName>#@pcname*#</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <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>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </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">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user #@adminName*# /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user #@adminName*# #@administratorPassword*#</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
        =========================
        OFFLINESERVICING SETTINGS
        =========================
        Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
        During this configuration pass, you can add language packs, updates, or other packages to the offline image.
        The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
        Packages listed in the servicing section of the answer file are applied to the offline Windows image.
        The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
        Additionally, you can use Package Manager with an answer file to install packages.
        -->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
        =====================
        AUDITSYSTEM SETTINGS
        =====================
        The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
        This results in fewer required images because a reference image can be created with a minimal set of drivers.
        The image can be updated with additional drivers during the audit process.
        You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
        For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
        See Reseal mode in oobeSystem.
        -->
    <!--
        <settings pass="auditSystem">
        </settings>
        -->
    <!--
        =====================
        AUDITUSER SETTINGS
        =====================
        The auditUser pass is similar to the auditSystem pass.
        However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
        Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
        See Reseal mode in oobeSystem.
        -->
    <!--
        <settings pass="auditUser">
        </settings>
        -->
    <!--
        =====================
        OOBESYSTEM SETTINGS
        =====================
        The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
        oobeSystem settings are processed before a user first logs into Windows.
        Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
        OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
        -->
    <settings pass="oobeSystem">

        <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">

            <TimeZone>#@system_timezone*#</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>#@adminName*#</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
        <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>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </component>

    </settings>
    <cpi:offlineImage cpi:source="wim:c:/temp/win10_/win10-x64/installfiles/sources/install.wim#Windows 10 Pro N" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>


Ich weiß nicht mehr weiter woran es liegen könnte.

Mfg

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 07 Jan 2020, 15:34

So ich habe das ganze auch nochmal mit der Version 1909 Probiert und auch hier dieselbe Fehlermeldung.
Ich habe auch mal in die Logs reingeschaut von dem "Start Setup" unter "x:\windows\panhter\setupact" und da finde ich komischerweise egal ob bei "Windows 10 1909 oder 1903" die selbe Fehlermeldung.
Bild

vllt. hilft das ja weiter?

Mfg

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 13 Jan 2020, 14:41

Hallo,

habe hier mal die "Unattend.xml" nachdem die "Antwortdatei" nicht gefunden werden konnte.

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
   ====================
   WINDOWSPE SETTINGS
   ====================
   The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
   For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
   -->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>0</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">      <Active>true</Active>      <Format>NTFS</Format>      <Label>WINDOWS</Label>      <Letter>C</Letter>      <Extend>false</Extend>      <Order>1</Order>      <PartitionID>1</PartitionID>   </ModifyPartition>      <ModifyPartition wcm:action="add">      <Active>false</Active>            <Label>WINPE</Label>      <Letter>X</Letter>      <Extend>false</Extend>      <Order>2</Order>      <PartitionID>2</PartitionID>   </ModifyPartition>
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>MH37W-N47XK-V7XM9-C7227-GCQG9</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>Name</FullName>
                <Organization>Orgname</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>Windows 10 Pro N</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>1</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>de-DE</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>de-DE</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   GENERALIZE SETTINGS
   =====================
   The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
   A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
   In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
   When a system is generalized, specific configuration data for a given installation of Windows is removed.
   For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
   The generalize configuration pass runs only when you use the sysprep /generalize command.
   Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
   -->
    <!--
   <settings pass="generalize">
   </settings>
   -->
    <!--
   =====================
   SPECIALIZE SETTINGS
   =====================
   During the specialize pass of Windows Setup, machine-specific information for the image is applied.
   For example, you can configure network settings, international settings, and domain information.
   The specialize pass is used in conjunction with the generalize pass.
   The generalize pass is used to create a Windows reference image that can be used throughout an organization.
   From this basic Windows reference image, you can add further customizations that apply to different divisions
   within an organization or apply to different installations of Windows.
   The specialize pass is used to apply these specific customizations.
   -->
    <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">
            <ComputerName>vm113573-test</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>XXX</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <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>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
        </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">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user Administrator /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user Administrator XXX</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
   =========================
   OFFLINESERVICING SETTINGS
   =========================
   Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
   During this configuration pass, you can add language packs, updates, or other packages to the offline image.
   The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
   Packages listed in the servicing section of the answer file are applied to the offline Windows image.
   The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
   Additionally, you can use Package Manager with an answer file to install packages.
   -->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   AUDITSYSTEM SETTINGS
   =====================
   The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
   This results in fewer required images because a reference image can be created with a minimal set of drivers.
   The image can be updated with additional drivers during the audit process.
   You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
   For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditSystem">
   </settings>
   -->
    <!--
   =====================
   AUDITUSER SETTINGS
   =====================
   The auditUser pass is similar to the auditSystem pass.
   However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
   Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditUser">
   </settings>
   -->
    <!--
   =====================
   OOBESYSTEM SETTINGS
   =====================
   The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
   oobeSystem settings are processed before a user first logs into Windows.
   Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
   OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
   -->
    <settings pass="oobeSystem">

        <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">

            <TimeZone>W. Europe Standard Time</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>Administrator</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>XXX</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c X:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
   <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>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
        </component>

    </settings>
    <cpi:offlineImage cpi:source="wim:c:/temp/win10_/win10-x64/installfiles/sources/install.wim#Windows 10 Pro N" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>



Hier der Log von "Work.cmd"

Code: Alles auswählen

'bcdboot x:\windows /v'
BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n
BFSVC: Using source OS version a000047ba0001
BFSVC: Copying boot files CopyBootManager(Yes) x:\windows\boot\PCAT -> \\?\GLOBALROOT\Device\HarddiskVolume2\Boot
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\bootmgr for read because the file or path does not exist
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\bootuwf.dll for read because the file or path does not exist
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\bootvhd.dll for read because the file or path does not exist
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\qps-ploc\memtest.exe.mui for read because the file or path does not exist
BFSVC: Copying font files from x:\windows\boot\Fonts to \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\Fonts...
BFSVC: Copying resource files from x:\windows\boot\Resources to \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\Resources...
BFSVC: SetNamedSecurityInfo failed! Error code = 0x2
BFSVC: Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume2\Boot\Resources\en-US\bootres.dll.mui for read because the file or path does not exist
BFSVC: Servicing debugger files
BFSVC: List of debugger files is empty
BFSVC: System partition is not in a space
BFSVC: BfsInitializeBcdStore flags(0x0000000c) RetainElementData:n DelExistinObject:n
BFSVC: VolumePathName for x:\windows is x:\
BFSVC: Opening template from \Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}\windows\System32\config\BCD-Template.
BFSVC: BCD Error: File is not system store. File: \Device\HarddiskVolume2\Boot\BCD Status: 0
BFSVC: BCD Error: Failed to open system store. Status: c0000098
BFSVC Error: BcdOpenStore failed with unexpected error code, Status = [c0000098]
'bcdedit /enum firmware'
The boot configuration data store could not be opened.
The volume for a file has been externally altered so that the opened file is no longer valid.
"Running in 64 Bit PE"
The boot configuration data store could not be opened.
The volume for a file has been externally altered so that the opened file is no longer valid.
Starting opsi-script ......


Falls noch welche logs benötigt werden einfach bescheid geben.

Ich habe auch alles bereits komplett neu gemacht
Opsi paket installiert von Repo.
Neue win10 Iso download
Win 10 ADK isntalliert mit PE addon
Iso und Winpe Ornder nach win10-x64 in jeweiligen Ordner kopiert
opsi-set-rights
Template nicht verändert alles original gelassen

Benutzeravatar
ThomasT
uib-Team
Beiträge: 226
Registriert: 26 Jun 2013, 12:26

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon ThomasT » 13 Jan 2020, 16:02

Hmm, der Teil hier ist doppelt drin:

Code: Alles auswählen

<component name="Microsoft-Windows-International-Core-WinPE"


Bei uns ist der aber im Template nicht doppelt...
Kein Support per DM!
_________________________
opsi support - https://www.uib.de/
For productive opsi installations we recommend support contracts.

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 13 Jan 2020, 16:14

Ich lösche mal die doppelte Zeile und versuche es gleich mal direkt aus

Aber woher zieht er sich das Template? ich habe doch das win10-x64 Paket neu von euren Repo installiert.

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 13 Jan 2020, 16:20

Okey das stand da gar nicht drinne da habe ich wohl falsch kopiert :?

Habe das gerade netboot win10-x64 starten lassen und in die unattend geguckt da steht die zeile nur 1 mal drinne
Hier nochmal die unattend (richtig kopiert) :D

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
   ====================
   WINDOWSPE SETTINGS
   ====================
   The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
   For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
   -->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>0</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">      <Active>true</Active>      <Format>NTFS</Format>      <Label>WINDOWS</Label>      <Letter>C</Letter>      <Extend>false</Extend>      <Order>1</Order>      <PartitionID>1</PartitionID>   </ModifyPartition>      <ModifyPartition wcm:action="add">      <Active>false</Active>            <Label>WINPE</Label>      <Letter>X</Letter>      <Extend>false</Extend>      <Order>2</Order>      <PartitionID>2</PartitionID>   </ModifyPartition>
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>MH37W-N47XK-V7XM9-C7227-GCQG9</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>Name</FullName>
                <Organization>Orgname</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>Windows 10 Pro N</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>1</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>de-DE</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   GENERALIZE SETTINGS
   =====================
   The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
   A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
   In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
   When a system is generalized, specific configuration data for a given installation of Windows is removed.
   For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
   The generalize configuration pass runs only when you use the sysprep /generalize command.
   Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
   -->
    <!--
   <settings pass="generalize">
   </settings>
   -->
    <!--
   =====================
   SPECIALIZE SETTINGS
   =====================
   During the specialize pass of Windows Setup, machine-specific information for the image is applied.
   For example, you can configure network settings, international settings, and domain information.
   The specialize pass is used in conjunction with the generalize pass.
   The generalize pass is used to create a Windows reference image that can be used throughout an organization.
   From this basic Windows reference image, you can add further customizations that apply to different divisions
   within an organization or apply to different installations of Windows.
   The specialize pass is used to apply these specific customizations.
   -->
    <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">
            <ComputerName>vm113573-test</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>XXX</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <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>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
        </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">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user Administrator /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user Administrator XXX</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
   =========================
   OFFLINESERVICING SETTINGS
   =========================
   Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
   During this configuration pass, you can add language packs, updates, or other packages to the offline image.
   The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
   Packages listed in the servicing section of the answer file are applied to the offline Windows image.
   The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
   Additionally, you can use Package Manager with an answer file to install packages.
   -->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   AUDITSYSTEM SETTINGS
   =====================
   The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
   This results in fewer required images because a reference image can be created with a minimal set of drivers.
   The image can be updated with additional drivers during the audit process.
   You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
   For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditSystem">
   </settings>
   -->
    <!--
   =====================
   AUDITUSER SETTINGS
   =====================
   The auditUser pass is similar to the auditSystem pass.
   However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
   Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditUser">
   </settings>
   -->
    <!--
   =====================
   OOBESYSTEM SETTINGS
   =====================
   The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
   oobeSystem settings are processed before a user first logs into Windows.
   Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
   OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
   -->
    <settings pass="oobeSystem">

        <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">

            <TimeZone>W. Europe Standard Time</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>Administrator</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>XXX</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c X:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
   <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>0407:00000407</InputLocale>
            <SystemLocale>de-DE</SystemLocale>
            <UILanguage>de-DE</UILanguage>
            <UILanguageFallback>de-DE</UILanguageFallback>
            <UserLocale>de-DE</UserLocale>
        </component>

    </settings>
    <cpi:offlineImage cpi:source="wim:c:/temp/win10_/win10-x64/installfiles/sources/install.wim#Windows 10 Pro N" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

xBr0th3rs
Beiträge: 13
Registriert: 03 Dez 2019, 15:47

Re: Windows 10 1909 Installation "Antwortdatei nicht gefunden"

Beitragvon xBr0th3rs » 17 Jan 2020, 11:53

Hat vllt. jemand für mich seine "unattend.xml" die nicht bearbeitet ist für "1903" oder "1909" das ich die mal abgleichen kann?

Weil es scheint mir als würde was an der "unattend.xml" nicht passen weil wenn ich im "Winpe" in der Konsole "..\win10_...\installfiles\setup.exe" ausführe startet es auch normal fürn Handbetrieb sobald ich aber noch "/unattend:x:\unattend.xml" dahinter ausführe kriege ich die fehlermeldung.
Die "unattend.xml" ist aber da.

Mfg