Recommended Posts

How-To Change Boot Screen on Win7

- First, Use ResHack with %windir%\system32\bootres.dll file

- Extract the RCData resource.

- So you have two files, one *.rc and another one *.bin

- Rename the file *.bin into *.wim (not win!!)

- Use 7zip to extract your *.wim file

- In the extracted files you have an xml witch describe the second file witch is the boot logon bitmap animation!!!

Now you can modify the logon animation! But be carefull, to have a correct xml description file!!!

After modifications, do the inverse procedure, with a backup of your original bootres.dll file.

I advise you to try on a virtual machine before!

PS : Microsoft do not recommend to change it!!!

Link to comment
https://www.neowin.net/forum/topic/806920-how-to-change-boot-screen-on-win7/
Share on other sites

  • 2 months later...
  • 3 weeks later...

I'm assuming this is the glowing Windows logo?

A bitmap can be "animated" by containing "frames" of the animation next to each other, the application reads a "frame" every so many pixels across or down the file. That's just speculation for me, I don't have Win7 RTM to try this out with.

  • 2 months later...
  • 1 month later...

How-To Change Boot Screen on Win7

- First, Use ResHack with %windir%\system32\bootres.dll file

- Extract the RCData resource.

- So you have two files, one *.rc and another one *.bin

- Rename the file *.bin into *.wim (not win!!)

- Use 7zip to extract your *.wim file

- In the extracted files you have an xml witch describe the second file witch is the boot logon bitmap animation!!!

Now you can modify the logon animation! But be carefull, to have a correct xml description file!!!

After modifications, do the inverse procedure, with a backup of your original bootres.dll file.

I advise you to try on a virtual machine before!

PS : Microsoft do not recommend to change it!!!

1) How do I put the modified image back into the *.wim archive (7zip shows an error message that reads "incompatible interface")?

2) How do I put the *.rc and *.bin (*wim renamed back into *.bin) back into the bootres.dll?

EDIT: Instead of extracting the *.wim with 7zip (7zip can't compress *.wim archives) it's better to mount it r/w with gimagex (you'll need to download the WAIK first), copy the *bmp file out, modify it, put it back into the archive and unmount it with the "commit changes" option.

I'm still wondering how to put the *.bin (*.wim archive) and *.rc files back into the bootres.dll.

I have been able to extract, manipulate and repackage this files. My question is this:

How are you certifying the file as proper by MS standards? I have been able to pull out the CERTIFICATE but after inserting it into the DLL, the system still won't recognize it properly (I am assuming this based on outcome of the process, Vista loading worm only).

The other option is this:

If you were to select NOGUIBOOT as in previous versions of Windows, what could we use to load a static image? Any thoughts on this?

Even better....how about a replacement for the Vista loading worm? any ideas on THIS? All I really need is for a static image to display in reasonable resolution. Anyone know of a location to "load" an image to get this to happen?

I am not opposed to searching google either. I have run a laundry list of searches that have given a thousand results, none specific enough to be considered really helpful. Figured I would bounce this off where I found the most helpful information.

-Surfer

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Vivaldi version 8.0.4033.50 released June 17: https://vivaldi.com/blog/desktop/minor-update-eight-8-0/
    • The Online part hasn't even been announced and probably won't be included on day one. This is a massive singleplayer game.
    • While I agree with all that, it just proves there's an a** built for every seat.
    • Lol are you mad because I'm not using AI? I'd rather pay people than lose a bunch of potential customers and get humilated because I used AI. A lot of people won't purchase a game if it used AI during development.
    • LibreWolf 152.0-1 by Razvan Serea LibreWolf is an independent “fork” of Firefox, with the primary goals of privacy security and user freedom. It is the community run successor to LibreFox. LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. This is achieved through our privacy and security oriented settings and patches. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. LibreWolf features: Latest Firefox — LibreWolf is compiled directly from the latest build of Firefox Stable. You will have the the latest features, and security updates. Independent Build — LibreWolf uses a build independent of Firefox and has its own settings, profile folder and installation path. As a result, it can be installed alongside Firefox or any other browser. No phoning home — Embedded server links and other calling home functions are removed. In other words, minimal background connections by default. User settings updates Extensions firewall: limit internet access for extensions. Multi-platform (Windows/Linux/Mac/and soon Android) Community-Driven Dark theme (classic and advanced) LibreWolf privacy features: Delete cookies and website data on close. Include only privacy respecting search engines like DuckDuckGo and Searx. Include uBlockOrigin with custom default filter lists, and Tracking Protection in strict mode, to block trackers and ads. Strip tracking elements from URLs, both natively and through uBO. Enable dFPI, also known as Total Cookie Protection. Enable RFP which is part of the Tor Uplift project. RFP is considered the best in class anti-fingerprinting solution, and its goal is to make users look the same and cover as many metrics as possible, in an effort to block fingerprinting techniques. Always display user language as en-US to websites, in order to protect the language used in the browser and in the OS. Disable WebGL, as it is a strong fingerprinting vector. Prevent access to the location services of the OS, and use Mozilla's location API instead of Google's API. Limit ICE candidates generation to a single interface when sharing video or audio during a videoconference. Force DNS and WebRTC inside the proxy, when one is being used. Trim cross-origin referrers, so that they don't include the full URI. Disable link prefetching and speculative connections. Disable disk cache and clear temporary files on close. Disable form autofill. Disable search and form history...and more. LibreWolf 152.0-1 changelog: Upstream release, see the Firefox 152.0 Release Notes Notable changes: The AppImages are now built on Codeberg along with the other releases We have decided to wait a bit longer to enable the settings redesign, due to use being aware of multiple upstream issues Download: LibreWolf 64-bit | Portable 64-bit | ~100.0 MB (Open Source) Download: ARM64 | Portable ARM64 Links: LibreWolf Home Page | Addons | Screenshot | Reddit Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      560
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      73
    4. 4
      Michael Scrip
      64
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!