- Joined
- May 1, 2017
- Messages
- 195
- Motherboard
- GA-Z170X-UD3
- CPU
- i7-6700
- Graphics
- GTX 1080
This is pretty weird, I guess.
I was running Windows 10 and macOS Sierra on dualboot on the same drive, everything was doing just fine until I came upon with this issue (http://imgur.com/E64XUBd) and decided to wipe macOS and just have Windows, so as we all know deleting every single partition on my SSD and doing a FRESH Windows 10 UEFI install is probably the best way to start fresh and ensure no leftover files from either operating systems / bootloaders are left in the system, so I just did that. Booted into the Windows USB installer, deleted every single partition on my SSD and installed Windows on the unallocated space left.
When I turned my PC off and turned it back on the next morning, the same error popped up, which was kinda confusing as I had done a completely fresh install. I was kinda lost so I made this thread (thinking it could have nothing to do with macOS nor Clover as I had already wiped those). http://www.tomshardware.com/forum/id-3443462/error-0x0000454-uefi-startup.html
I did countless of solutions instructed on the web and by the guy who replied to my post there, but nothing seemed to work.
Something weird happened next, when I was about to enter the command prompt to enter a couple of commands I was instructed to enter, for whatever reason I clicked on "Use a device", only to find an entry named "Clover start boot.efi at Sierra SSD. Please check the following pictured for better understanding.
http://i.imgur.com/5MZNbcV.jpg
http://i.imgur.com/2vYGHtY.jpg
How can I still have Clover leftovers if I completely wiped my SSD? Something tells me the issue is caused by Clover still hanging out in my system when it should have been completely gone, as this boot error was the reason I decided to just run Windows and delete macOS.
Thanks!
I was running Windows 10 and macOS Sierra on dualboot on the same drive, everything was doing just fine until I came upon with this issue (http://imgur.com/E64XUBd) and decided to wipe macOS and just have Windows, so as we all know deleting every single partition on my SSD and doing a FRESH Windows 10 UEFI install is probably the best way to start fresh and ensure no leftover files from either operating systems / bootloaders are left in the system, so I just did that. Booted into the Windows USB installer, deleted every single partition on my SSD and installed Windows on the unallocated space left.
When I turned my PC off and turned it back on the next morning, the same error popped up, which was kinda confusing as I had done a completely fresh install. I was kinda lost so I made this thread (thinking it could have nothing to do with macOS nor Clover as I had already wiped those). http://www.tomshardware.com/forum/id-3443462/error-0x0000454-uefi-startup.html
I did countless of solutions instructed on the web and by the guy who replied to my post there, but nothing seemed to work.
Something weird happened next, when I was about to enter the command prompt to enter a couple of commands I was instructed to enter, for whatever reason I clicked on "Use a device", only to find an entry named "Clover start boot.efi at Sierra SSD. Please check the following pictured for better understanding.
http://i.imgur.com/5MZNbcV.jpg
http://i.imgur.com/2vYGHtY.jpg
How can I still have Clover leftovers if I completely wiped my SSD? Something tells me the issue is caused by Clover still hanging out in my system when it should have been completely gone, as this boot error was the reason I decided to just run Windows and delete macOS.
Thanks!
