I think I know how to fix it for win10 but will require re-writing all files to change location of images including registry entries. It will take me some time but I should have a solution this weekend sometime. I went back to win8.1 so I dont have to use vmware for my tools...that was a pita. lol Plus my school works with win8.1 which is good. I will keep everyone posted on progress.
If you updated to win10 home edition then you cant activate legit if upgrading to win10 pro edition. Win10 is tied to you hardware id's and that would be on M$ activation server showing legit for home edition only. You would need to use kms activator. The ei.cfg allows user to choose either home or pro editions in window. From my experience with win10 th2 builds, I didnt have to add it to the multi editions. I dont know if it is no longer required but never hurts to add it anyways. With the new th2 version we are all learning so I dont know everything. Trial and error.
I have some time this morning so doing some testing with vmware oem for win10 x64 th2 testing...if it works then will edit the rest of the oem's.
Win10 x64 th2 wont allow even at logon to insert reg entry to add oem logo to system properties. hmmm Might have to skip it since win10 x64 th2 doesnt allow it. You can do it once desktop is up but that isnt a ideal solution. Any suggestions from anyone is welcome. lol I was thinking of possible current user instead of local machine run once reg entry. Back testing...
I installed Win10 Home x64 TH2 right now on VMware (no OEM mod just normal vm) and the background image shows up when it reaches desktop... Note that I used a Win10 aio ok? Installed offline and local user account and special crafted $oem$ to make use of abbodi's KMS activator.
Then I will keep this for myself since no one else has issue like I do. I will fix it so it works with my machine in vmware and just hang on to it if I need it for other ppl computers. Seems everyone is saying it works but for myself and BALTAGY it doesnt work. Maybe in a couple years M$ will get win10 stable but by then there will be a new OS out. This really frustrates me because win10 is so hit and miss with different configs. Makes it seem like I am lying and I am not. I am done with sharing issues I encountered with win10 since only me and BALTAGY are the ones with the issues. BALTAGY, I will send the new build to you in pm to see if it corrects your issues as well as mine.
Mr.X can you share you iso build name and hashes. I am wondering if ppl are saying online that these are msdn when they might be insider builds. I have read controversy over the builds released and wonder if that is why some experience issues and other dont. Please share info on the iso you are using. This is the one I am testing but I added the oem project to it so hashes wont be match... en_windows_10_multiple_editions_version_1511_x64_dvd_7223712.iso
Same as some have sysprep issues & others don't. At the moment if I create a provisioning package Windows can't reset. Without 1 it works fine. This has only happened with the latest 1511 build. Simple things like this should not be so hard!
I expect an new build iso soon since M$ issues are hit and miss. This makes it hard on me. lol Morning time and I am wanting a beer already. lmao! What I am trying to do is make the project work regardless of M$ issues but it is turning out to be a pita. I have made progress but soon as I post progress someone pops up saying nothing is wrong and it works so what do I do? lol We now know why M$ made it free upgrade...its still beta or should I say alpha. Back to "my" testing...
My install source is a tailored AIO, by me lol It uses the es-mx isos released by M$ (originals) Btw I forgot to mention I integrated: windows10.0-kb3105211-x64 windows10.0-kb3103688-x64 So it reaches BuildExLab: 10586.3.amd64fre.th2_release_sec.151104-1948
If you want me to share my AIO with you? Only 4.6 GB This way you can make a proper dissection of it lol
Maybe the fixes you added addressed those install install issue ppl like myself are having. Either way, win10 is a half a** OS and it will take a year or better before stable. Obviously not much testing done in these area's we are discussing. My issues with my lappy (win10 only): -cant enter audit mode with xml file during install. -background changes every time I insert usb drive. -setting dont hold in control panel. -internet disconnect issues. -shutdown issues. -now oem branding issues with th2 release. Went back to win8.1 after three months and everything works again. If it isnt broke, dont upgrade. lol
Your not the only one having issues with 10 and $oem$ stuff mate. Been fighting it for the last few weeks. Everything works nice and smooth on 7 & 8 but 10 just goes out of its way to stop things working. Spoiler My SetupComplete basically checks to see what ver of Windows it is, wether its activated or not, if MOEM hasnt or wasnt able to insert certs itll start Dloader if tis 7 or a KMS if its 8 or 10. It then calls a cmd for SetACL to take ownership of some reg keys and files, some regs to disable UAC and tweak a few things then copy over some files (depending on the OS). Then it runs Office 2016 setup (using a custom .msp) and a KMS for me before rebooting. Works 100% perfect on about a dozen PCs Ive tested with on 7 and 8. 10 kills it in several different ways. Firstly it ignored any regs to disable checking for updates, if it needed to reboot for a critical update it would kill SetupComplete and reboot straight to the desktop. Then I got round that to find the final 'Just a moment' screen is hard coded 'On-Top' so I couldn't see the Office setup (merged the isos so it has the menu for Pro, Viso and Project before the custom msp kicks in) Got round that to find that it was either resetting ACL's or reverting reg entries when the User first 'logs in' before the desktop. Sick of it, simple things which have been around for donkeys, all with practical real world use for admins etc, it feels like MS are going out of there way to make it as awkard as possible to do this sort of stuff now.
Tried HKCU for run once at logon and still fails to insert reg entry. Going to try schtask now... With my past experience with settings not holding I am wondering if M$ messed up the OS really bad. Seems some folders are locked down from system and reg locations as well. Maybe I should I just want until next M$ release which I expect soon?
Well the registry string works for me "Logo"="C:\\ProgramData\\Asus\\images\\logo.bmp" is your like the above?
i call my oem.reg like this from OOBE @echo off IF EXIST %windir%\HKCU.vbs reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v Run1 /t REG_SZ /d "%windir%\HKCU.vbs" /f >nul start /w regedit /s %systemroot%\setup\scripts\OEMInformation.reg del /F /Q %systemroot%\setup\scripts\OEMInformation.reg PM with your email and i can send you my folder zipped up of you like