Debombing non fbl_partner_eeap windows 10 builds

[Jake harrison]

Hi I'm currently running a bat file which is removing the digital signature from every exe file in the C directory of windows server build 10154 which doesn't boot on the current date if this doesn't let me boot on the current date what else could I do to allow booting on the current date? I willing to try anything.

[yourepicfailure]

Once you strip signatures, you must boot with the disable driver signature enforcement flag set.
You will have to do this every time.

[Voyambar]

Once you strip signatures, you must boot with the disable driver signature enforcement flag set.
You will have to do this every time.

Can't you set that permanently somehow? I remember a place saying you could once

[yourepicfailure]

I think it is "Test Mode." Web search "enable test mode" and give that a try. Maybe it'll work.

I'm interested in this as I'd like to get 9909 running past expiration.

[Jake harrison]

I think it is "Test Mode." Web search "enable test mode" and give that a try. Maybe it'll work.

I'm interested in this as I'd like to get 9909 running past expiration.

Sadly it didn't work, I think some vital system files like winload.exe require a digital signature to boot properly. On boot it no longer says a part of the system has expired it goes into automatic repair.

[johndoe123]

I think you will need to sign winload.exe to debomb.

[gtgamer468]

Even then, you would have to deal with activation. You can get away with older TP1 builds as Windows 8.1's tokens can be used. I'm a bit unclear though about builds that move more away from 8.1 RTM in later builds.