This is abit weird. Switched back to v60. It gave me the same errors but worked. Sort of, it doesnt detect basebord info (vendor, product, model name etc) OS is W8. AVG is installed and used as main protection but its not updated, also Defender is inactive. I know this computer is dirty but not sure if that would slow down or make QT fail Reinstall is coming up tho.. Edit: its recognized as Acer
The baseboard etc is all read from the registry which should not trigger any AV as it not writing anything only to variables. Maybe some of the registry/file system has got the permissions messed up? It is also possible some of the DMI entries have non standard characters such as & " ^ ( ) > < etc which will cause havoc with any script. Not used AVG for many years (v7.1 i think way way back lol). Now Avast has hold of it no idea what pleasures they added, i know Avast was quite keen back in the day, probably more so now.
the last digits bit i added as i know the QT is used in other threads and this little addition can help working out which key was used, be it OEM-SLP, gVLK, (not MAK keys though), etc.
UEFI boot (usb drive with two partitions for that matter made in rufus) MRP Project in Install.wim Install.wim contains a sysprepped version of Windows 10 x64 Pro 1803 MRP doesnt run in OOBE, no logs and the files are still there:/ Ideas? I was stupid enough to remove the iso before I could run it in a VM...
huh? I never use ei.cfg and OOBE.cmd runs just fine. ISO are from Media Creation tool I deployed W10 x64 Home/pro using MDT. It works fine in WDS and vmware but I could guess its different? Also languages didnt work but thats cool
Just put the ei.cfg from the download project folder and it will work. If it still won't work then there is something corrupted. When mxman2k gets home, he will check in. ps, can you run the QT on that install and post the saved report here?
Hmm odd about oobe not running within a install.wim If it is placed in [install.wim]\Windows\Setup surely it would be detected? Windows Setup should of 'seen' it... Unless it was installed via DISM or another way then i am unsure how it would react as the standard way via the $OEM$.... works. I wonder if the oobe.cmd needs to be outside of the wim? I have never added the project inside a wim before.
Well as it has a MSDM for W10 Asus Home/Core then ei.cfg would be needed to prevent setup from bypassing the oobe.cmd. If there is only home/core in the install.wim then you may see the selection screen to install Home, if it has only one edition it should just install home then MRP would insert the MSDM key. Or copy the Home MSDM key into the PID.txt and place that file within Sources, Setup will then run oobe.cmd, install Home/core and MRP will detect the PID.txt. Don't use the Insert PID.txt option, well you could but not needed as MRP will then detect the MSDM and insert the key that pc has for Home as normal. Hard to explain easy but i made MRP adaptable - but that no use if oobe stage gets bypassed because of a MSDM present.
Packard Bell it probably used the SLIC name as Acer bought Packard Bell as PBell only went up to Vista 2.0 SLIC. Pbell had some strange DMI entries that may of been the reason why it confused things. Some have PBell some Packard Bell - the old laptop i have here of that era confused QT too because for some strange reason they put ( ) in and borked out the return variable!