Its not the script. TH2 brought some changes, mainly deleteing the registry keys and info folder, where the images are stored, during and before first logon. Wether this is intentional my MS we have yet to see. Its also happening to some of us on 7 & 8 that use a slip streamed wim. It could possibly be a small update or change that MS is issuing to remove branding from PCs now. A lot of OEMs are also shipping them unbranded so this could be the way thats its headed. Alphas
I have tried applying settings later (setupcomplete.cmd and first logon reg entry) with no success. What I am trying to do now is if info folder not present, echo to log file about compatibility issue present. Testing this method now. Maybe in a year M$ will add support for my system. Alphawaves system brand changer works from desktop environment so end users still have an option until M$ next big update which is basically a install (will wipe out branding during this update/install).
Because the multi oem project works on some but not on others tells me its a compatibility issue not M$ targeting this project. This also explains why when I install win10, my bios setting for visualization gets disabled and I have to turn it back on manually for vmware to work in windows 10. Comes back to compatibility in the end.
I was trying not to use that tool. Its for network admins to give remote install permissions. I would not be able to include it in the project because its a M$ tool but if it does work I could post link to it and have end users add it themselves to the scripts folder. I will try later today and see results. Going to add a check if the project fails because of this as a second precaution to let end users know why it fails.
I added all reg entries and oobe folder permissions from within the script...now to add the %MAN%.reg file entries for permissions. One step at a time.
@mxman I do the same, I call cmd which sets the perms on This PC, Desktop Context menu, Recycle Bin as well as permissions on a few bits of garbage like Globiization leftovers in 7 and the built in wallpaper in all versions of Win. Much faster to do it via SetupComplete than mount the wim, set the perms and delete etc @The_Guardian - Slowly and surely kicks MS's ass...
Since I added the SetACL and set permissions, the script now fails when trying to apply the first reg entry. grrr
I corrected script and it works but the reg entries and info folder is still deleted. I can move the info folder to another location BUT it makes no difference if reg files cannot stay applied. Again, I dont know if it is my incompatible system or M$ themselves stopping the branding. Either way, I am done since I cannot address this issue on my machine. Link will stay down because there is no need for noobs to complain to me when they should be complaining to M$. I am done. Thread can be locked as far as I am concerned. Nothing I can do...
I am trying one last option and if that fails then will add to log file explaining. I will eventually upload links again but testing further to put my mind at ease. Either way, the project will be back. I am getting frustrated, sorry to all members. Beer makes everything better. AA is for quitters. Before anyone jumps on that comment, its just a joke.
Tried schtasks but that uses SYSTEM to run as well which is what is blocking branding. The SYSTEM is useless! There is no way for me to query username for schtasks run as user from oobe.cmd because it isnt setup yet. Cant use any of the runonce either hklm or hkcu. Cant use the start folder because it is setup after user sets up account. There is NO way to address this issue other then adding to the end of log file if failure occurs it either because of incompatible hardware or due to slipstreaming. This is the best I can do. I also added some error handling I noticed in other OS's that dont have certain schtasks like in win10 for the WinTel.cmd file. Because of the changes over the last few days and reverting back I want to test all OS's before making link available again on first post. M$, you win with the branding but you lost a customer. Over time as more ppl move away from windows then M$ will get their head out of the a**. All this over branding, really? Your call. With windows 10, you get what you paid for (most of us got the free upgrade). Windows 10 is worse then windows ME ever was.
Don't like the look of this. I feel we should be able to take care of it somehow though I saw your pm just now. The way I do the branding is by using the ps version of reg add however that is during post install. I feel I should flip the theme, manufacturer info, etc to the setup phase to see what happens. I feel we should be able to find a big enough hammer to smash it with.
I am all out of tools in the toolbox. The SYSTEM doesnt allow branding changes (info folder and all reg entries whether by regedit.exe or reg.exe). You find a solution please share with me. I have no hair left on my head. lol
The project has a x64 bit bug I need to address so hold off if needing to do a install on a x64 system. x86 systems are fine to use this on. Will update as soon as tests are done on my end. Sorry about that. Update: Corrections made, testing win 7 x64 now...
Good to hear . Keep at it should be able to take care of that bug in no time at all. Apart from it being a branding issue it probably does take some time to smash bugs cause of the VMing process.