Hi folks,
I’ve got an issue that I can’t seem to solve. I’m attempting to install a fresh copy of Windows 10 on an ASUS Vivobook Flip 14 – model TP410UA. I've used 6 different drives (2 SSD’s, 2 Hybrid HDD’s, and 2 standard HDD's), all of which are new and/or known good. Every attempt I’ve made with every drive has resulted in the following error:
“We couldn’t install Windows in the location you chose. Please check your media drive. Here’s more info about what happened: 0x80300024.”
If I listed everything I’ve tried, it would probably make for a long read for you. So, I'll just suffice to say I’ve exhausted all my expertise, and every suggestion I could find on Google, to no avail.
Here’s some things I’ve tried:
I suspect the motherboard may be the culprit, but it appears to be functional in every other respect. I would definitely appreciate any suggestions you could send my way.
Thanks!
I’ve got an issue that I can’t seem to solve. I’m attempting to install a fresh copy of Windows 10 on an ASUS Vivobook Flip 14 – model TP410UA. I've used 6 different drives (2 SSD’s, 2 Hybrid HDD’s, and 2 standard HDD's), all of which are new and/or known good. Every attempt I’ve made with every drive has resulted in the following error:
“We couldn’t install Windows in the location you chose. Please check your media drive. Here’s more info about what happened: 0x80300024.”
If I listed everything I’ve tried, it would probably make for a long read for you. So, I'll just suffice to say I’ve exhausted all my expertise, and every suggestion I could find on Google, to no avail.
Here’s some things I’ve tried:
- As mentioned, 6 known good drives
- Updated BIOS to version 309
- Full BIOS reset
- Load Optimized Defaults
- Fast Boot enabled/disabled
- CSM enabled/disabled
- Secure Boot enabled/disabled
- Tried 1909, 2004, and 20H2 versions of Windows 10, both Home and Professional
- Created new install media using both USB flash drives and DVD
- Tried all USB ports for connecting install media
- Tried all drives in uninitialized, initialized, unformatted, and formatted states
I suspect the motherboard may be the culprit, but it appears to be functional in every other respect. I would definitely appreciate any suggestions you could send my way.
Thanks!
Last edited: