- Joined
- Jun 24, 2015
- Messages
- 8,323 (2.30/day)
- Location
- Western Canada
| System Name | ab┃ob |
|---|---|
| Processor | 7800X3D┃5800X3D |
| Motherboard | B650E PG-ITX┃X570 Impact |
| Cooling | NH-U12A + T30┃AXP120-x67 |
| Memory | 64GB 6400CL32┃32GB 3600CL14 |
| Video Card(s) | RTX 4070 Ti Eagle┃RTX A2000 |
| Storage | 8TB of SSDs┃1TB SN550 |
| Case | Caselabs S3┃Lazer3D HT5 |
Hi all. I had a Win 10 installation going since the 28th of July but it wasn't very clean. After hearing reports that using the ISO would not necessarily net an automatic activation, I decided to "reset" windows (aka clean install from within, called "refreshing" in Win 8.1).
Big mistake.
I ran into the 0xc0000098 error. Basically it tells me that it can't boot, presumably because UEFI is broken / boot file is broken or missing / Windows Boot Manager is smoking weed. This kept happening so I made one of my S102 USBs a Win 10 installer and went into repair tools. I seemed to have fixed it by the method mentioned in this link https://neosmart.net/wiki/0xc0000098/#Fix_48120c0000098_in_Windows_8 and it continued to reinstall Windows 10 automatically. All things OK here. Got into Windows, had some quirky problems with default language but managed to switch it back. Said I needed to restart so I did.
Boom. Light blue screen. 0xc0000098 error.
I saw it and I hurled a flashlight across the room, so fortunately it was made of metal and the shelf was tough so no damage incurred. Holy shit, Windows. Holy shit.
At this point, the most immediate option is to run command prompt again and hope it boots up. But if it doesn't, I'm boned. The Win 10 installer on the USB prompts for an activation key, and the only one I found in my upgraded installation was a generic key with a string of 0s, which could not have been it. I have no way of knowing if 10 did clean install properly, because although it did display a whole lot of free space and looked like nothing was wrong, there clearly is something wrong with my boot configuration. I'm thinking that it's either to do with the main installation @ C: or the System Reserved partition, which I think is 450MB by default on my Intel drive.
Please, any help would be appreciated. I'll do my best not to get on the phone with MS in the meantime and make one of their reps permanently deaf. I wonder when they'll ever learn and not have a gong show of an OS release.
Big mistake.
I ran into the 0xc0000098 error. Basically it tells me that it can't boot, presumably because UEFI is broken / boot file is broken or missing / Windows Boot Manager is smoking weed. This kept happening so I made one of my S102 USBs a Win 10 installer and went into repair tools. I seemed to have fixed it by the method mentioned in this link https://neosmart.net/wiki/0xc0000098/#Fix_48120c0000098_in_Windows_8 and it continued to reinstall Windows 10 automatically. All things OK here. Got into Windows, had some quirky problems with default language but managed to switch it back. Said I needed to restart so I did.
Boom. Light blue screen. 0xc0000098 error.
I saw it and I hurled a flashlight across the room, so fortunately it was made of metal and the shelf was tough so no damage incurred. Holy shit, Windows. Holy shit.
At this point, the most immediate option is to run command prompt again and hope it boots up. But if it doesn't, I'm boned. The Win 10 installer on the USB prompts for an activation key, and the only one I found in my upgraded installation was a generic key with a string of 0s, which could not have been it. I have no way of knowing if 10 did clean install properly, because although it did display a whole lot of free space and looked like nothing was wrong, there clearly is something wrong with my boot configuration. I'm thinking that it's either to do with the main installation @ C: or the System Reserved partition, which I think is 450MB by default on my Intel drive.
Please, any help would be appreciated. I'll do my best not to get on the phone with MS in the meantime and make one of their reps permanently deaf. I wonder when they'll ever learn and not have a gong show of an OS release.