How to tweak monotonous cold "Welcome" message at logon

fergusd · 25 Jun 2023

I don't want to force you guys to watch a "How To Tweak Windows 10" YouTube video - you are probably better equipped to present them than to watch them! But I have followed
How to change the welcome text in Windows 10? - YouTube
to the letter - basically editing C:\Windows\System32\en-GB\winlogon.exe.mui using Resource Hacker, re-compiling it then re-introducing it to its directory. Still I am getting the stubborn "Welcome" one-word greeting at logon.
The author of the video logs in with a pwd. Here I am the sole user and Administrator and I just switch on and Hey Presto there I am without the requirement for a pwd. (This is deliberate, not a slip.) Would that make a difference?
Do any of you have a better / different method for this tiny but oh so desirable tweak?
Thank you!
Edition Windows 10 Pro
Version 22H2
Installed on ‎04/‎10/‎2020
OS build 19045.3086
Experience Windows Feature Experience Pack 1000.19041.1000.0

dalchina · 26 Jun 2023

Are you sure you have both hacked the file correctly, and saved it successfully to its correct location, overcoming any restrictions in doing so?

Note that hacked system files are very likely going to be replaced when using SFC /SCANNOW, or on any in-place upgrade repair install or major upgrade.

Paul Black · 26 Jun 2023

Hello @fergusd,

I actually did that using Win 7 a few years back. It was an interesting experiment.

@dalchina is exactly right when he says about the system files, well for Win 7 at least as I have NOT done this on Win 10. Keeping an updated System Image might help.

I hope this helps.

Compumind · 26 Jun 2023

Lol.

Is it even worth the effort?

dalchina · 27 Jun 2023

I guess I might call that a 'welcome' comment...

Easy way to replace system files- do it when Windows isn't running.

E.g. boot to a command prompt or boot PC from a live boot disk. No special techniques required.

garlin · 27 Jun 2023

Worked for me, but the whole process of replacing winlogon in Recovery console can be bypassed.

1. Copy \Windows\System32\[locale]\winlogon.exe.mui to a temp folder.

2. Edit with ResHacker (don't forgot to hit "Compile", before saving the file).

3. Download PowerRun, this grants TrustedInstaller rights to your CMD shell. No more access denied errors!

4. Open CMD from PowerRun. You can't overwrite a file that a running process is using, but you're allowed to rename it. This trick allows you to copy or move the edited version as a replacement.

Code:

cd \Windows\System32\en-us
ren winlogon.exe.mui winlogon.exe.mui.OLD
copy \Users\GARLIN\Documents\winlogon.exe.mui .

5. Restart Windows, since you can't kill the currently running winlogon.exe process.

TairikuOkami · 27 Jun 2023

Compumind said:

Is it even worth the effort?

Indeed, if it were merely a cosmetic change, whatever, but it can compromise security. But it is user's choice.

fergusd · 29 Jun 2023

Thanks to all esp Garlin for the effort and the personal touch.
I am pretty certain that I re-compiled correctly; and the "new" edited .mui file is there in place.
I used a Linux boot disk to achieve the out-of-Windows replacement.
So far still no success. It's not obvious (to me, anyway - not that that's a reliable indicator) that the PowerRun approach will work where the Linux pathway failed, but I will certainly give it a go - and check re-compilation.
Grateful thanks for all Tips and Tricks.
Fergus