Multi OEM/Retail Project

The info folder doesnt get created thus background image doesn't show in win 10 th2 x64 bit only. The x86 version installs correctly.

Testing fix now in vmware 12...

 

Ok, here is a progress update...
Win10 th2 x64 deletes the info folder after the oobe.cmd script is ran. Why? Only M$ knows. The only way to stop win10 th2 x64 from doing this is to lock it down during the installation for x64. Back to testing...

 

Well, I havent not be able to get the images to stay in the oobe\info directory. Funny this only happens with the win10 th2 x64 versions. I tried copying over the info folder to systemdrive and back during windows logon cmd via registry entry and it always gets deleted. I am beginning to think this new th2 x64 version has issues since it is the only version being effected or M$ doesnt want ppl to change the default theme. I need to think about this one because a workaround is needed, if its possible.

 

Already tried that through runonce reg entry and no go. Trying something new now...will keep you updated.

 

Has anyone tried Alphawaves system brand changer from windows 10 th2 x64 install to apply oem branding? I know it works from desktop but more concerned if it works with switches from oobe.cmd. I can manually add images from desktop also but need to choose vmware theme for it to apply. This isnt the solution obviously. I have tried take ownership with icacls, even changed attribute to read only and the info folder always gets deleted. With this being said, I wonder if windows 10 th2 x64 installer looks specifically for the info folder name? I will look into this...

 

You need to login to view this posts content.

 

Well it doesnt seem you can create or put any folder (any name) or files in the oobe folder. I will have to totally redo the project with info folder in another location to see if it then works. I will have to test all supported OS's again to make sure this doesnt affect them as well. This will take a lot of time to redo the "whole" project and do all the testing so have patients. I hate Win10!

I am going to do one more test to see if other win10 x64 builds are the same as the x64 retail build. I want to know if this one is the only one with issues.

 

Seems M$ removed audit mode also in th2 build or my lappy cant access it through xml. I think M$ is stopping the oem branding from here on out. Maybe that is why oem's are not using full branding in win10 like back with win8.x and win7. Seems M$ only wants their own images with the new th2 builds.

Testing enterprise x64 th2 edition to see results...

Update: All win10 x64 builds do not allow for anything to be put into the oobe folder.

 

Think I might leave the theme and system info branding out for x64. M$ is against oem's editing their images. If a complaint, contact M$.

This is a issue with all x64 bit versions of win10 th2. I expect the same eventually with win10 x86 versions in the near future.

Now we know why oem's never included the extra branding for win10 like in this project. M$ gave them the heads up seems like.

I am going to leave the multi oem project as it is since M$ win10 th2 removes the info folder anyways. No real need for me to remove scripting just for win10 only...M$ does it for me. I have spent hours trying to find a work around with no luck. If you are wanting full oem branding, dont use win10.

Personally I am going back to win8.1 and since M$ assigned my oemdm key to win10 through hardware id's, I will use kms activation so screw Win10.

 

M$ would make a butt load of money for charging to go back to win8.x or any other windows version if they were smart. lol I will be offline for a while to redo my system back to win8.1. My system ran great with it. I will install start is back for start button but that isnt a biggie since I own the app. Win10 doesnt even work with my school very well. I always have to contact tech. support and even they told me to go back to win8.x and everything will work again with my school. I am taking their advice after all the headaches. I am done with win10 permanently.

 

You can no longer use xml to enter it for a oem install of drivers and such. It error's on the x64 versions. You can do it from desktop of course but most things done in audit mode and branding are no longer available from an install point of view. I have been working on this for two days constant and have ran into one problem after another with win10 x64 editions. I am now back to win8.1 and it OEM ACTIVATED even though M$ said not possible after 30 days of using win10. They are not correct. I ran win10 for around 3 months and went back to win8.1 oem core today. I am very happy.

Note: I know most think generally about these issues regarding win10 but since th2 update, M$ stopped a lot of things we use to be able to do during INSTALL (not talking about anything from desktop).

 

Then I guess my experience has been a lie and I am senile. lol Win10 is so hit and miss I went back to win8.1 so I care less about win10 now.

My wifes lappy has no issues with win10 but my lappy hates it. Better days now with win8.1. I will never recommend win10 from now on.

I love how ppl say things work but not work for others. lol Anyways, water under a bridge.