Can't update or use expired develop preview

Windows 10 build. One day out of nowhere, got error on boot stating that a component of the operating system has expired winload.efi. Any resolution I could find always referenced tricking the OS by rolling back the system date in the bios, getting it to at least boot, then quickly updating the build. For over a week, I couldn't even get passed the first step. I would change the bios date, try to boot, and either get the same exact "your pc needs to be repaired" message as above, or one about "process1 initialization failed". I would get the second one instead after trying various things from forums in the windows 10 RE cmd prompt. Everything from chkdsk to sfc /scannow to dism commands and bootrec commands. Same result. Eventually, I think I found the work around. A post mentioning that a bootstat.dat removal or renaming may allow a boot. So I tried this, and TADA....I finally got the ******* to boot. Here's the thing: I can run some very basic functions and programs, but ANYTHING related to system and update in windows 10 fails with the exact same message always: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

I get this trying to open windows update, settings, command prompt, even trying to launch the windows setup.exe from a windows 10 dvd to try and upgrade. So I have access to the system, but I can't update the build, install/update windows via installer or even run any commands from prompt which basically leaves me crippled. The easy answer is that the system date is wrong. But in a classic damned if you do/don't...If I put the system date back to normal, i'm back to square one with the expired component winload.efi error

I should also add a little detail I expect to get asked about to save time. This is a dual boot desktop, 2 copies of windows 10 on seperate HDD. To answer the next obvious question of "If you have a working copy of windows 10, why do you care about the other one so much". The answer is that I have a LARGE amount of programs and tools installed that I don't want to loose access to. Either I no longer have access to the installer/missing license which takes re-install off the table, or I have alot of configuration and integration that would be a nightmare to start from scratch. And that's if by a miracle I can track down all the various directories. Although I have only the two OS, the pc holds partitions spanning 15+ years of hardware and versions of windows (Yes....I am cursing myself for not organizing and consolidating instead of just straight 1:1 copy)

If it came down to no other possible choice, I would accept a re-install if that meant I lost zero files but would loose some programs. But as it stands, I couldn't even launch the windows 10 dvd without that same error

I also realized I haven't been here for a while and my system specs were for a wrong pc. Updated my system specs if anybody needs the data for the question. So again, I DO have access to at one of the windows 10 installs and do have install media, both dvd and usb based. So if any ideas revolve around replacing files, I will have access to the problem install directory. And assuming the usual first answers: Yes i've already tried running startup repair, system restore (claims there are no restore points although that shouldn't be the case), reset (says the disk is locked or gets a generic failed message with options to shutdown or go back to advanced options (re tools). bootrec /fixmbr, bootrec /rebuildbcd. re-install obviously only gives the option for a clean install, which is a no go since I cannot loose the files and the other option won't run unless you trigger it from windows after boot. Trying to return to previous build just gives straight up failure message.

If there is an option whereby I could somehow transfer or backup the programs and deploy them on the different or new install, I'm game. I don't know if there is a way to transfer programs or image them in a way that they can be deployed again