Wanted to try something new and learn a bit.Īcross the board, I tried so many freaking distros, the unified problems were SMB permissions, automount of SMB shares doesn't really work consistently no matter what the hours of googling and trial and error showed me. Really low-end, worked great for years, but didn't want to hold onto Win7 forever, and win10 didn't like 4gb RAM, and I was tired of Windows issues since I deal with it all day at work. It's an i3-4010u Intel NUC with 4gb RAM, 128gb ssd. Here's my Linux experiment with just getting a fucking HTPC+RetroGameEmulation system reinstalled. I appreciate it's a combination of errors there (yes they're very old laptops, yes we probably could've watched our updates more) but I just wanted to highlight it, if it helps one person it's worth it. The error message was "Windows cannot verify the digital signature for this file" for system32\winload.exe and so we couldn't boot.įortunately, we've found a workaround by getting an old copy of c:\windows\system32\winload.exe from a machine that's not updated, getting the machine into recovery mode with a USB stick and copied it into the impacted machine. All the laptops impacted were configured for Legacy Boot but machines on UEFI seems fine. Our users had the original version of this update installed in March '19 but the September update to the patch states it updates "boot manager files to avoid startup failures" which is what we encountered.
It needs KB4474419 first but it turns out this KB has been updated multiple times since it first came out in March '19 and our SCCM only distributed the original version of the patch so please check yours.
We bricked downed approximately 80 Windows 7 machines today rolling out January 2020 KB4534310.
0 kommentar(er)
