Longhorn TweakNT?

Discuss Windows Vista, 7, 8.x, 10 and Windows Server 2008, 2008R2, 2012, 2016, 2019, Home Server, SBS 2008, SBS 2011.
Post Reply
Posts: 20
Joined: Mon Feb 12, 2018 11:44 pm

Longhorn TweakNT?

Post by Pikavolt321 »

What would happen if you changed the SKU/Edition of a Longhorn build? Anything from 4066 to 4074 to 5048 to even Beta 1-2 builds. For example, would a Longhorn 4074 .NET Server break everything like when you TweakNT XP? Would the activation freak out if 4066 became a client build? What about all of the Longhorn Professional builds like 5048 and 5112/5219? And other editions like Media Center Edition, Home Edition, Tablet PC?

Posts: 160
Joined: Mon Feb 03, 2020 5:28 am

Re: Longhorn TweakNT?

Post by Meow »

Nothing really would happen. You’re just changing registry. 4066 would become a client build and would identify as such. Activation would simply work as if it was on an actual client build. At worst activation might just shut down entirely, and you won’t be able to log in.
Try switching the windows 3.0 ega driver with windows 1.01’s. it will be fun.

User avatar
Posts: 1238
Joined: Mon Jul 23, 2012 9:40 pm
Location: Flying high in a DC10

Re: Longhorn TweakNT?

Post by yourepicfailure »

I broke 4033 using it to try and convert it to Tablet PC edition.
You still won't get the components enabled anyways- you'd have to install them yourself.

With the winlogon hack, activation isn't called at all anymore. So it won't be a problem.
"C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off"
You will never tear me from the grasp of the Pentium M!

FTP Access
Posts: 51
Joined: Wed Sep 25, 2019 10:12 pm

Re: Longhorn TweakNT?

Post by Voyambar »

Can't you just convert the SKU to volume and just have it stop calling activation or delete it entirely automatically?

Post Reply