Question Failure during APPLY_IMAGE operation

KublaiKhan

Distinguished
May 24, 2015
365
3
18,815
0xC1900101-0x2000C
The Installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation


Doesn't this mean there's an old driver that is incompatible with the Windows 10 installation?

I'm wanting to install Windows 10 Pro on my old rig, replacing Windows 7 Home. I purchased a key directly from Microsoft. The image is on a flash drive. I put the appropriate PID.txt with the key in the \Sources folder.

The process halted with a black screen with the first restart. I had to cycle power. That's when the error appeared. Yesterday, I had trouble installing new drivers for a new GTX 1660 Super on the same machine.

I've disconnected every extra internal HDD other than my bifurcated C: and D: drive (D: has all my Steam stuff on it). I disconnected my external USB drives. There is no working hardware connected other than a mouse and keyboard. The Ethernet cable is connected.

To me, it seems the installer is trying to upgrade the old OS, rather than create a fresh installation. We used to format hard drives when installing Windows, and I assumed I would, today. Does the new installer prevent it? Would formatting C: stop this error message?

Anyway, I read that some people tried installing Windows 10 on older rigs without success. I hope that isn't going to happen here.

i7-950
EVGA 131-GT-E767-TR LGA 1366 SLI3
DDR3 12 GB RAM 1600 MHz
 
Last edited:
I'm wanting to install Windows 10 Pro on my old rig, replacing Windows 7 Home. I purchased a key directly from Microsoft. The image is on a flash drive. I put the appropriate PID.txt with the key in the \Sources folder.

The process halted with a black screen with the first restart. I had to cycle power. That's when the error appeared. Yesterday, I had trouble installing new drivers for a new GTX 1660 Super on the same machine.

I've disconnected every extra internal HDD other than my bifurcated C: and D: drive (D: has all my Steam stuff on it). I disconnected my external USB drives. There is no working hardware connected other than a mouse and keyboard. The Ethernet cable is connected.

To me, it seems the installer is trying to upgrade the old OS, rather than create a fresh installation. We used to format hard drives when installing Windows, and I assumed I would, today. Does the new installer prevent it? Would formatting C: stop this error message?

Anyway, I read that some people tried installing Windows 10 on older rigs without success. I hope that isn't going to happen here.

i7-950
EVGA 131-GT-E767-TR LGA 1366 SLI3
DDR3 12 GB RAM 1600 MHz
If you are trying to maintain your previous installation of Windows 7 then it would be doing an upgrade.
If not, go ahead and format C: so that it performs a clean installation of the OS itself.
 
If you are trying to maintain your previous installation of Windows 7 then it would be doing an upgrade.
If not, go ahead and format C: so that it performs a clean installation of the OS itself.
No, I am NOT trying to save my old Windows 7 installation. I've backed everything up on other drives. I want to get rid of the old installation and install a brand new Windows 10 Pro installation. I paid $200 for that key, and I want to get something out of the deal!

I could not figure out how to get the Windows 10 installer (on a flash drive) to perform a clean installation (as in the old format C: and then install Windows process we followed for years). I just never see the option!

I just created a repair disc on an optical drive. I think I can use that to format C:, if that's what it takes.

Thanks for any help you might offer!
 
I could not figure out how to get the Windows 10 installer (on a flash drive) to perform a clean installation
Do this, and exactly this....
 
  • Like
Reactions: KublaiKhan
Windows is getting installed by restoring a generic pre install image of windows to the drive you specify.
You can do it manually by running this command, E would be you dvd drive and G the drive you want windows on.
I'm not suggesting you to do it manually since you could really screw things up, this is just info on your issue.
For the image applying to fail there went something wrong and sadly it could be anything from bad ram to bad drive to just the stars being badly aligned.
I would google the error code and see what other people did to fix it.
It's very unlikely for it to be a driver issue, as long as it can detect the drive it's just a copy operation.

dism /Apply-Image /ImageFile E:\Sources\install.esd /index:1 /ApplyDir:G:\

Edit: very quick googling showed that it might be a space issue, how large is your C drive?
 
Windows is getting installed by restoring a generic pre install image of windows to the drive you specify.
You can do it manually by running this command, E would be you dvd drive and G the drive you want windows on.
I'm not suggesting you to do it manually since you could really screw things up, this is just info on your issue.
For the image applying to fail there went something wrong and sadly it could be anything from bad ram to bad drive to just the stars being badly aligned.
I would google the error code and see what other people did to fix it.
It's very unlikely for it to be a driver issue, as long as it can detect the drive it's just a copy operation.

dism /Apply-Image /ImageFile E:\Sources\install.esd /index:1 /ApplyDir:G:\

Edit: very quick googling showed that it might be a space issue, how large is your C drive?
Yeah . . . Google has not been helpful with the issue. I did try to fix this on my own before bothering you guys, but was quickly overwhelmed by the stunning lack of clarity and insight regarding a problem that's been around since 2012 and 2013.

The C: and D: drive is a 1TB hard drive, split right down the middle, so C: is 465 GB. That's more than enough for Windows 7, and more than enough for 10. I don't use the C: drive for much other than running the operating system. All my data goes to other physical drives.

There are any number of suggestions for my issue. Again, this isn't something new. People had the same error code and message ten years ago. How it is that no one has nailed the problem down in ten years staggers my limited imagination.

Anyway, I'm gonna try the clean installation procedure suggest by USAFRet. Wish me luck! Worst case, I buy a new rig. I can't run Windows 7 any more.
 
Last edited:
Oh, my.

I created the flash drive months ago, following the procedure listed in the guide, above. I also downloaded an ISO, but that thing requires double-layer optical media, of which I have none.

I changed the boot order to start with USB, but the computer keeps bypassing the flash drive and starting Windows 7, normally.
 
Oh, my.

I created the flash drive months ago, following the procedure listed in the guide, above. I also downloaded an ISO, but that thing requires double-layer optical media, of which I have none.

I changed the boot order to start with USB, but the computer keeps bypassing the flash drive and starting Windows 7, normally.
Then it would seem your flash drive is not properly constructed.
Nothing valid to boot from.
 
For a Win 10 or 111 install, it only needs to be 8GB or larger.
I created a second USB installer, which also fails to boot.

One of the boot options in my old BIOS is REMOVABLE, so I assumed I could boot from USB. Perhaps I cannot?

Would this work if I burned the .ISO I also created months ago to a double-layer DVD? I know the machine boots from optical, as that is how Windows 7 was installed years ago.
 
I created a second USB installer, which also fails to boot.

One of the boot options in my old BIOS is REMOVABLE, so I assumed I could boot from USB. Perhaps I cannot?

Would this work if I burned the .ISO I also created months ago to a double-layer DVD? I know the machine boots from optical, as that is how Windows 7 was installed years ago.
Created how, exactly?
 
Created how, exactly?
Well, I used the MediaCreationTool22H2, of course! :)

I also formatted the USB stick with the NTFS file system, and started yet another installer tool setup, in case it was not booting because it had been formatted using exFAT. I also just read something that makes me think I misunderstood my old BIOS. That old BIOS may not consider a USB stick as REMOVABLE media, but as a subset of HARD DRIVE.

I will let you know . . . .
 
Well, I used the MediaCreationTool22H2, of course! :)

I also formatted the USB stick with the NTFS file system, and started yet another installer tool setup, in case it was not booting because it had been formatted using exFAT. I also just read something that makes me think I misunderstood my old BIOS. That old BIOS may not consider a USB stick as REMOVABLE media, but as a subset of HARD DRIVE.

I will let you know . . . .
Using the MCT, there is no issue about how it was formatted before.

The MediaCreation tool completely reformats the flash drive as it needs.
 
Using the MCT, there is no issue about how it was formatted before.

The MediaCreation tool completely reformats the flash drive as it needs.
Thanks! Good to know!

I just learned a bit about my BIOS. USB was at the bottom of the priority chain, under the physical hard drives, within the Hard Disk Boot Priority menu (which I haven't looked at in years). Furthermore, I did not realize I could hold down ESCape during boot to switch boot order without going through BIOS. Now I know.

I've already launched the installer from USB, so it will work.

I'm gonna go nuke my C: drive. Fingers crossed!
 
That has not been a problem for a couple of decades. Seriously.

Clicking the wrong thing?
No, you caught me during mid-edit.

I figured the whole ESCape key thing out, and used that to boot from USB.

I've got to figure out the whole Microsoft / Local account thing out. Windows Security is forcing me to enter my Microsoft Account information just to access the shared USB drive connected to my router—yet another old issue resurfacing with the new Windows 10 installation!
 
Last edited:
No, you caught me during mid-edit.

I figured the whole ESCape key thing out, and used that to boot from USB.

I've got to figure out the whole Microsoft / Local account thing out. Windows Security is forcing me to enter my Microsoft Account information just to access the USB drive connected to my modem, which was not the case earlier today!
Why is the USB drive connected to the modem?
 
Why is the USB drive connected to the modem?
Router. We have a shared "network" hard drive connected to the router. Let's everyone in the house share a large music library and such.

Sorry for the confusion.

I can't access the drive at all, now. After mapping it in Windows 7, I never had to enter any sort of password. Windows 10 wants a user name and password, with no indication of where that is supposed to come from. Clearly, there is more to figure out.
 
Router. We have a shared "network" hard drive connected to the router. Let's everyone in the house share a large music library and such.

Sorry for the confusion.

I can't access the drive at all, now. After mapping it in Windows 7, I never had to enter any sort of password. Windows 10 wants a user name and password, with no indication of where that is supposed to come from. Clearly, there is more to figure out.
For the OS install, connect that flash drive directly to the PC.
Boot from that.
 
Router. We have a shared "network" hard drive connected to the router. Let's everyone in the house share a large music library and such.

Sorry for the confusion.

I can't access the drive at all, now. After mapping it in Windows 7, I never had to enter any sort of password. Windows 10 wants a user name and password, with no indication of where that is supposed to come from. Clearly, there is more to figure out.
When setting up a network share windows always sets up network credentials, try this on one of the PCs that still has access to the usb on the router to see what credentials you need.
It could also be a password of the router though so look through its menu as well.
 
This migration from Windows 7 to Windows 10 did not go smoothly. I must have wiped the C: drive and installed four or five times to get to this point. What I've learned:

You cannot just run the Windows 10 installer from the USB stick while in Windows 7 and expect good things to happen. The installer will NOT provide a fresh installation; rather, it will perform an upgrade in this case. It tried to upgrade my existing Windows 7 Home to Windows 10 Home—I paid for a Windows 10 Pro key. I'm sure some people have had good luck with upgrades, but I believe a fresh installation on an empty drive is the better choice. Whatever the case, you must BOOT from either USB or DVD to perform a fresh Windows 10 installation.

The Windows 10 installer seems to try really, really hard to use old drivers and old resources from previous installations. I had to delete my old partitions, including the tiny "hidden" partitions, to get the Windows 10 installer to perform what I would expect to be a fresh installation of Windows 10 Pro.

Windows is going to install the NVIDIA High Definition Audio drivers whether or not you want it, because the little speakers built into your monitor are best, naturally!

Windows will install old video drivers.

You may very well lose video during POST and be unable to see BIOS screens when switching to DisplayPort or HDMI under Windows 10 and 11. This also means you can lose the ability to boot to USB, because you cannot see to navigate the associated menus. Using older standards, such as DVI, long enough to install new video drivers can prove a tremendous boon. Don't throw those old video cables away!

Windows 10 takes issue with optical drives. . . . or the cables I had were hot garbage, and broke down when touched one time too many. They did come with the motherboard, so they were probably garbage. Anyway, BIOS sees my two optical drives; Windows 10 only sees one, and I'm not sure that one drive is even working properly. Naturally, they worked fine under Windows 7.

Windows 10 takes issue with USB hard drives. It only recognizes them once in a while.

Windows 10 is a privacy nightmare. I don't even know where to begin . . . .
 
Last edited:

Latest posts