+InsaneNutter MVC Posted June 25, 2015 MVC Share Posted June 25, 2015 Can anyone else replicate this? I appear to be able to break EFI based Windows 10 Build 10130 VM's running on Hyper V very easily. If you go to Settings > Time and Language > Date and time then turn off "Set time automatically" Now try to change the date / time using the button below, windows will crash. On reboot the blue screen error will state: "Your PC/Device needs to be repaired A component of the operating system has expired File \windows\system32\winload.efi Error code: 0xc0000605" This is on an EFI based Virtual Machine running under Hyper V, Windows 8.1 Pro is the host OS. I've submitted feedback on this issue anyway. Link to comment Share on other sites More sharing options...
Jackaluichi Posted June 25, 2015 Share Posted June 25, 2015 OK, so here's the thing. I have a dual boot setup on my Desktop PC (Windows 10 build 10130 + Windows 8.1), and I faced a similar bug yesterday. In my case, I reckon it was triggered after moving my disk drives to a different SATA3 controller on my motherboard. Here's a photo (sorry for the bad quality): So, what do you think? Are these similar enough? Link to comment Share on other sites More sharing options...
Eric Veteran Posted June 26, 2015 Veteran Share Posted June 26, 2015 @InsaneNutter: I don't think yours is a bug. Winload just thinks your preview evaluation is expired due to the time. @jackaluichi: Your error code indicates that winload could not be found where it was expected. You might be able to fix it by bringing up the EFI boot menu on your board at POST and selecting the drive you wanted it to boot from. (Also check and make sure your settings are trying EFI before looking for MBR.) Link to comment Share on other sites More sharing options...
Jackaluichi Posted June 26, 2015 Share Posted June 26, 2015 @InsaneNutter: I don't think yours is a bug. Winload just thinks your preview evaluation is expired due to the time. @jackaluichi: Your error code indicates that winload could not be found where it was expected. You might be able to fix it by bringing up the EFI boot menu on your board at POST and selecting the drive you wanted it to boot from. (Also check and make sure your settings are trying EFI before looking for MBR.) Yeah, I already tried all of that. I forgot to mention I'd already sorted out, but I had to wipe out my entire SSD because no matter what I tried, it was impossible to bring back the modern blue dual boot screen. Link to comment Share on other sites More sharing options...
+InsaneNutter MVC Posted June 26, 2015 Author MVC Share Posted June 26, 2015 @InsaneNutter: I don't think yours is a bug. Winload just thinks your preview evaluation is expired due to the time. I did think that, however i never actually altered the date, so it was still the 25/06/15. Link to comment Share on other sites More sharing options...
PGHammer Posted June 29, 2015 Share Posted June 29, 2015 I did think that, however i never actually altered the date, so it was still the 25/06/15. A similar issue happens between EFI and non-EFI operating systems on a non-EFI computer - I have the problem where OS X and Windows have their system clocks differ by five hours, despite identical settings as far as time management. Both Windows and OS X have settings for NTP servers - however, OS X uses only ntp.apple.com, while the settings for Windows is changeable by the user (while the default is time.windows.com - and has been since XP - this can be changed to any of several optional LISTED NTP servers, or users can add their own; I use time.nist.gov, which is in the default NTP list in Windows 10). As a result, I have to correct-on-the-fly the time in Windows if I run OS X for an extended period. It's not difficult; however, it IS a pain in the rear to do. Link to comment Share on other sites More sharing options...
Recommended Posts