-Replaced WinTel.cmd host file entries with route command. plz what's the difference between the two .?
If users wish to view from "admin cmd prompt" the ip's listing from the WinTel.cmd file, you can type... ROUTE PRINT If user wish to remove a route that was added with the WinTel.cmd file, you would type... ROUTE DELETE 123.123.123.123 (for an example) More info can be found by typing from "admin cmd prompt"... ROUTE /?
Testing the new updated win10 1607 now in vmware to see if everything works. Will also test the WinTel.cmd file as well. One step at a time. Update: -Project installed correctly. -WinTel.cmd installed correctly. Back to vacation.
Since Redstone OEM user account picture does not show up at login screen and OEM theme is not selected automatically. With TH2 there was no problem.
Please read my sentence exactly. The user account picture does not show up at _logon screen_. When I check 'settings->accounts->your picture' it is there. Cannot post pictures, therefore please use the "links"(space in it) I post -> http: //i67.tinypic.com/fddipx.jpg About theme: Instead of just using the OEM theme (shown as "windows default theme" on control panel->personalization) is creates and uses a new theme called "unsaved theme" with different (non-customized/transparent) color though background/lock screen show/apply correct OEM images. That it creates a new theme under "my themes" may be correct but previously (Win10 TH2) it used exact same naming/showed up the little "badge" like the OEM theme under "windows default theme". Is a minor issue of cosmetic nature. More important for me is the missing user account picture at logon screen. "Link" -> http: //i63.tinypic.com/k6tzo.jpg Activation did not change anything. Optional customization of project "optional" folder not used at all. Project log file: 04.08.2016 11:33:59,18 Project Version Date: 06-29-2016. ---Hardware incompatibility and slipsteaming has been known to cause branding failures--- 04.08.2016 11:33:59,18 Files present and extracted successfully. 04.08.2016 11:33:59,19 OEMs folder found successfully. 04.08.2016 11:33:59,21 Defined Windows 10 Pro x64 version Professional editon found. 04.08.2016 11:33:59,99 Defined HP manufacture found for branding and possible activation. 04.08.2016 11:34:01,30 OEM-DM key ------------------------CYRYC present and applied. 04.08.2016 11:34:02,39 License Status: Error, not licensed. 04.08.2016 11:34:02,39 Force theme text file not present. 04.08.2016 11:34:10,12 Syspdt=HP ProBook 650 G1 found and applied successfully. 04.08.2016 11:34:10,12 Backgrounds folder created successfully. 04.08.2016 11:34:10,12 Deletion of OOBE.xml file successful. 04.08.2016 11:34:10,12 User.bmp backed-up and replaced successfully. 04.08.2016 11:34:10,12 User.png backed-up and replaced successfully. 04.08.2016 11:34:10,12 User-40.png backed-up and replaced successfully. 04.08.2016 11:34:10,12 User-32.png backed-up and replaced successfully. 04.08.2016 11:34:10,14 User-48.png backed-up and replaced successfully. 04.08.2016 11:34:10,14 User-192.png backed-up and replaced successfully. 04.08.2016 11:34:10,14 Theme backed-up and replaced successfully. 04.08.2016 11:34:10,15 Img100.jpg backed-up and replaced successfully. 04.08.2016 11:34:18,17 Advanced logon screen for win 10 enabled successfully. 04.08.2016 11:34:18,17 Info folder created successfully. 04.08.2016 11:34:18,17 Files moved to System32\oobe\Info folder successfully. 04.08.2016 11:34:26,18 RunOnce reg entry added successfully. 04.08.2016 11:34:26,18 Script has completed successfully.
Thanks Alpha. Remember to edit the oem-dm key if in log file so others cant steal your key. Not saying anyone here would but you never know.
I have a legit Win10 OEM machine (previous post was Win8 OEM). I try it again this evening and post results.
I have a Toshiba laptop in that came with win 10 Home, i had to replace the screen and hard drive due to the 'user' dropping said laptop! I just installed win 10 home and the project didn't run, realised i forgot about the ei.cfg as it just installed home and it bypassed the project run stage grr. So just Re-installing W10 Home again (with ei.cfg to choose home). Will post results within 30-45 mins once it has installed. Wish i had a spare SSD would be so much quicker lol. So this will be a fresh install and not a upgrade over the original TH2. LAN is connected so should auto activate before desktop (fingers crossed). Would you like a copy of the logs? I can post the projects log file (obscuring the msdm key) and if required i can run the Query tool and post those results too. Mx
Is this mandatory? Because until now I always did setups from scratch without having lan cable plugged on installation.
If not a legit win10 machine (win10 oem-dm key in bios) then yes it is mandatory. If users did a upgrade then your win10 is activated by retail means which needs internet to check activation via M$ servers. @mxman2k, Yes, please provide the projects log file and query tool results.txt file. Just make sure to edit your oem-dm key. I want to thank everyone who is helping with testing the new win10 version and posting feedback.
If the LAN isn't connected then the project will run as normal but because the pc wasn't connected to the internet to check the key or digital licence it wont be activated before the desktop appears and will give false results for this test. As wifi will not be connected during setup only a lan connection will let the setup 'see' the internet. Mx edit @The_Guardian - You beat me to the reply
Having lan cable plugged did not bring user picture back to logon screen on my W8 machine. Will see what happens on W10. Guardian, I have to thank you for this project
On your win8.x machine, if you use kmspico or similar then after it is activated go into the settings and change pic to the oem image you wish under %ProgramData%\Microsoft\User Account Pictures\. You will have to show hidden files in order to point it to that location. Reboot and your image should show. That is what I did in vmware and it worked. If not activated from oobe then you will have to do it manually. There is no reg entry for this because M$ has locked it down pending activation. Note: If you used the upgrade to win10 promotion then insert your retail key (if you backed it up) in the pid.txt file and also add the Retail.txt file to the project then add it to the iso then it "should" activate in theory but you will need to be online so it can check key on M$ servers. You will need to set version to core or pro as well with the ei.cfg file. I dont know if it will work this way with the upgrade promotion but worth a shot. Since M$ uses retail keys for the upgrade promotion this method "should" work.
Hmmm very odd results! Project.log gave this : 04/08/2016 17:07:26.78 Project Version Date: 06-29-2016. ---Hardware incompatibility and slipsteaming has been known to cause branding failures--- 04/08/2016 17:07:26.80 Files present and extracted successfully. Which is very very strange as this is an untouched ISO i downloaded from the Microsoft site last night! The only thing 'modified' is the ei.cfg file and the $OEM$ folder ??????????? Query Tool Results attached (with MSDM key obscured - win7 key is the normal SLP key as i never entered any key at all during setup or after. Mx
Did you choose the upgrade or custom when installing win10? If upgrading turn off AV or Windows Defender then try again. I know some have had issues with the new version not upgrading correctly so that might be why. I seen you sig and had to quote it...lol