coded version or not Thanks for the reply Alphawaves, Don't meen to beat a dead horse but just to clarify. Is the file I downloaded coded Version v1.2.1 or is it version v1.0.2.1 as image shows. h xx p:// postimg.org/ image/ d6g5r1il9 placed spaces for i cant post images yet
Hi Lauriz, sorry for confusion yep its v1.0.2.1. v1.2.1 is this version its just me being lazy. Ive updated the update url check so it no longer says 'v1.0.2.2 update available' EDIT: Code: System Brand Changer.zip = SHA-1: 56062709AA54F2ED26107F2384D5F2C1E336D457 System Brand Changer.exe = SHA-1: 06F6C5C2647612AD7891552835EB90FA06104BF0 These hashes are correct
Only Windows 10 pre 14393 Builds. v1.0.2.2 may have started and changed a background or two in build 14393 and later but it basically failed to do its job. Which is why i reverted back to previous version, updated it and released it as v1.0.2.1!
Hello my friends, i have this problem: i have integrated Multi-Oem in iso file ( isoroot\source\$OEM) windows 10, i have installed in mod sysprep on vhd virtual box and i have backuped it with ghost. I have recoverd it on others motherboard but when i repeat OEM rebranding with System Brand Changer, at reboot or logout user my system wont stard and i have grey screen only with cursor without image. can i resolve it? Thanks
Hi! This has never failed me, but I noticed this version will not changed the SYSTEM LOGO for Windows 10 v1703, only the OEM LOGO.. Might there be a work-around or a new version that will enable this? Thanks in advance and thanks for a great utility!
Forgive me if I missed it, but is there a way to automate this? Basically, I use FOG to deploy an image and would like this to run as an automated post install task.
Strange to see v1.0.2.1 doesn't run on v1809 build 17763 (shows not supported warning) , but v1.0.2.2 runs fine.