TONT 42993 修改Windows启动界面的LOGO

改头换面的代价。

原文链接：https://blogs.msdn.microsoft.com/oldnewthing/20030805-00/?p=42993

This is the answer I give to IT people when they ask if it’s okay to customize the Windows boot logo.

有位IT人士问我自定义Windows启动画面的LOGO能不能行，这是我给他的回答。

DO NOT DO THIS ON A PRODUCTION MACHINE OR YOU WILL REGRET IT.

不要在生产环境下这样做，否则你会后悔的。

If you hack the bitmap everything will seem fine until six months down the road when you decide to install the latest service pack. The service pack installer will not upgrade your ntoskrnl because it looks at the file and says “Hm, this isn’t the standard uniprocessor ntoskrnl, it’s not the standard multiprocessor ntoskrnl, it’s not the standard advanced server ntoskrnl, I can’t tell what this is, so I don’t know which version of ntoskrnl to update it to. I’ll just leave it alone.”

如果你决定这样做，跑到资源文件里修改了（启动画面的）位图资源，看上去并没有什么问题，直到过了六个月之后你决定安装最新的Service Pack。Service Pack的安装程序将不会更新你的ntoskrnl，因为：安装程序检查了一下，心里想，『嗯，这不是普通的那个Uniprocessor ntoskrnl，不是标准的Multiprocessor ntoskrnl，也不是标准的Advanced Server版的ntoskrnl。我不知道它到底是那个版本的，所以不知道应该用哪个版本的升级文件来更新它。告辞。』

If you are lucky you will bluescreen at boot because the old ntoskrnl is incompatible with some other critical part of the service pack.

比较幸运的话，你会在引导的时候BSOD（蓝屏），因为旧版的ntoskrnl与经过Service Pack更新后的某个系统关键组件不兼容。

If you are unlucky, your machine will appear to run normally when in fact it is quietly corrupting itself, and then it will keel over or generate bogus data when you least expect it.

反之，你的机器看上去是正常运行了，但实际上它正悄悄地搞坏自己，迟早有一天会跪，或者发生输出乱七八糟的数据这种你最不愿看到的情况。

If you planned ahead, you will have quit your job and moved to Hawaii so the disaster falls on your replacement’s head to clean up while you sit on the beach sipping a pina colada.

如果你对此早有准备的话，趁早辞职并搬家到夏威夷去吧，这样等哪天（因为你更新LOGO导致ntoskrnl版本不兼容（而且貌似还在正常运行）时）就可以躺在沙滩上喝着饮料，而接你班的人可就惨了。