How to set a OEM logo in NTLite?
- Thread starter A_Dub
- Start date
-
- Tags
- logo oem windows 10
Hello, would be interested in that too!
As far as i know the oemlogo.bmp has to be saved to C:\Windows\system32
In the passt i`ve done that by booting the image and saving the bmp to that location. then sysprep an DISM. But thats quite unhandy for only the OEM Logo
How can this be achieved with NTLite? with the OEM Information function in unattended settings?
thank you very much in advance!
As far as i know the oemlogo.bmp has to be saved to C:\Windows\system32
In the passt i`ve done that by booting the image and saving the bmp to that location. then sysprep an DISM. But thats quite unhandy for only the OEM Logo
How can this be achieved with NTLite? with the OEM Information function in unattended settings?
thank you very much in advance!
C
Clanger
Guest
I'd like to add Dell oem stuff to my laptops.
Settings doesn't display the OEM logo after W10 1607. It's only visible from Control Panel -> Settings.
Why bother if you can't see it?
Note the double-slashes in Logo's path. When you have the image loaded, open the Explore mount directory and copy your BMP file to Windows\System32. Apply your changes.
Why bother if you can't see it?
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation]
"Manufacturer"="Winaero"
"Model"="Winaero-PC"
"SupportHours"="8.00 AM - 16.00 PM"
"SupportPhone"="111-222-333"
"SupportURL"="http//winaero.com"
"Logo"="C:\\OEM\\Winaero.bmp"Note the double-slashes in Logo's path. When you have the image loaded, open the Explore mount directory and copy your BMP file to Windows\System32. Apply your changes.
C
Clanger
Guest
garlin i've had a look at your $oem$ pack then the $oem$ folder in the dell model specific iso and ive worked out what i can ditch, local packs drivers and a few updates. Setupcomplete.cmd runs before oobe.xml yes? can i add the entries in that to setupcomplete then delete oobe.xml or just keep oobe.xml, i will be using an answer file.
Sod it, i'll just tweak the oem pack then add it as is, thats how dell does it. Thank you for your help
Sod it, i'll just tweak the oem pack then add it as is, thats how dell does it. Thank you for your help
Last edited by a moderator:
C
Clanger
Guest
Can i add Computer name, Full computer name, Computer description info as a reg file?
Dell is forced to run Setup using the OEM guidelines, it boots into audit mode (does its job) and copies an answer file for OOBE Setup.
You're not an OEM, and get to ignore this.
1. Copy Dell logos -> $OEM$\$$\System32\OEM
2. Copy Dell wallpapers -> $OEM$\$$\web
3. Dell's answer file is replaced by this equivalent reg file.
You're not an OEM, and get to ignore this.
1. Copy Dell logos -> $OEM$\$$\System32\OEM
2. Copy Dell wallpapers -> $OEM$\$$\web
3. Dell's answer file is replaced by this equivalent reg file.
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Start Menu]
"OEMLogoUri"="file://%SystemRoot%\\system32\\OEM\\MceLogo.png"
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\OEMInformation]
"Logo"="%SystemRoot%\\system32\\OEM\\SystemLogo.bmp"
"Manufacturer"="Dell"
"SupportURL"="http://support.dell.com"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes]
"DesktopBackground"="%SystemRoot%\\web\\wallpaper\\Dell\\Win7 LtBlue 1920x1200.jpg"
"ThemeName"="Dell"
"WindowColor"="FROST"
"BrandIcon"="%SystemRoot%\\system32\OEM\\ThemeLogo.png"
"DefaultThemesOff"="false"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat\WindowsExperienceIndexOemInfo]
"Logo"="%SystemRoot%\\system32\\OEM\\PerfLogo.bmp"
"HardwareUpgradeURL"="www.dell.com"
C
Clanger
Guest
Got it 
I might mediafire the basic barebone oem pack save others downloading 7.17GB just for 4.6mb of files.
Those dell iso's are pretty much redundant as they are not updated to eol let alone esu builds.
I might mediafire the basic barebone oem pack save others downloading 7.17GB just for 4.6mb of files.Those dell iso's are pretty much redundant as they are not updated to eol let alone esu builds.
Last edited by a moderator:
HP's OEM image uses a normal reg file.
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation]
@=""
"Manufacturer"="Hewlett-Packard"
"Model"=""
"Logo"="\\windows\\system32\\oobe\\info\\hp_BADGE.bmp"
"SupportPhone"="1-800-474-6836 (1-800-HP-Invent)"
"SupportURL"="http://www.hp.com"
"SupportHours"="In the United States, 24 hours a day, 7 days a week"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Start Menu]
"OEMLogoUri"="file://c:\\windows\\system32\\oobe\\info\\hp_MCE_LOGO.png"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat\WindowsExperienceIndexOemInfo]
"Logo"="\\windows\\system32\\oobe\\info\\hp_BAR.png"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background]
"OEMBackground"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes]
"Drop Shadow"="FALSE"
"Flat Menus"="FALSE"
"SetupVersion"="10"
"InstallTheme"="%WINDIR%\\resources\\Themes\\OEM.theme"
"InstallVisualStyle"="%ResourceDir%\\Themes\\Aero\\Aero.msstyles"mainauraap
New Member
- Messages
- 1
- Reaction score
- 0
Why there is no option in Nlite apps that select the bmp file for Oem logo and wallpaper need to upgrade the application
- Messages
- 1,199
- Reaction score
- 236
NTLite would have to "upload" the image, then store it in a directory/folder and also modify the associated registry keys for it to work
For wallpaper, it's very quick with Post-Setup (Post-Setup (Before Logon) - Add - File - Image path)
For OEM, few people are interested, maybe
Last edited:
My original comment in post #4 applies:
To change the logo from winver requires replacing a bitmap from "C:\Windows\Branding\Basebrd\basebrd.dll". NTLite won't do that on principle since that's considering hacking a Windows executable or DLL file.
To change the logo from winver requires replacing a bitmap from "C:\Windows\Branding\Basebrd\basebrd.dll". NTLite won't do that on principle since that's considering hacking a Windows executable or DLL file.