9907 Timebomb

Discuss Windows Vista, 7, 8.x, 10 and Windows Server 2008, 2008R2, 2012, 2016, 2019, Home Server, SBS 2008, SBS 2011.
Post Reply
kat346
Posts: 1
Joined: Mon Sep 07, 2020 8:01 pm

9907 Timebomb

Post by kat346 »

Out of pure curiosity, Is it possible to swap out the files from fbl_ie to fbl_awesome1501, to get rid of the timebomb completely, since the two builds are nearly identical and the only possible difference is the x64 and x86 versions, is it possible? or is the x86 a big barrier in to achieving this?

Applegame12345
User avatar
FTP Access
Posts: 178
Joined: Sun Dec 13, 2015 6:14 am
Location: C:\Users\Applegame12345

Re: 9907 Timebomb

Post by Applegame12345 »

kat346 wrote:
Mon Sep 07, 2020 8:05 pm
Out of pure curiosity, Is it possible to swap out the files from fbl_ie to fbl_awesome1501, to get rid of the timebomb completely, since the two builds are nearly identical and the only possible difference is the x64 and x86 versions, is it possible? or is the x86 a big barrier in to achieving this?
No, it's not possible to swap out files from fbl_ie to fbl_awesome1501. While you can do that, it will do absolutely nothing because 9907 fbl_awesome1501 is flight signed (meaning everything relies on signature of files, even winload.exe is signature checked). If you go past the timebomb date, the build stops booting. This doesn't happen to fbl_partner_eeap/fbl_ie/th2_sigma_grfx_dev/and other labs because they are test-signed. AFAIK flight-signing was dropped in mid-RS2 (build 14965 is the first Insider build to boot on current date). Since then every single Win10 build boots on current date.

TL;DR: No, you can't get 9907.fbl_awesome1501 or any other TH1/TH2/RS1/RS2 builds (until 14965) to run on current date. Don't bother.
Image
Discord: @Applegame12345#0023
>>click here<< for some wiki editing

Post Reply