If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
I may get only one chance to unbrick this system, so I am asking first.
https://u.cubeupload.com/luFNrN.jpg In another thread we (Paul, Doomsdrrzej, Wolf K, dogs, etc.) discussed how to recover when Microsoft Windows Update bricked a Win10 Pro boot disk which was working up until the moment of the automatic Windows Update. https://u.cubeupload.com/g3waOf.jpg This thread is just asking the procedure, which "Cameo" did (but who hasn't responded) for using DISM to attempt a recovery of the Microsoft-bricked HDD. http://i.cubeupload.com/2qpmmt.jpg Paul has found the following recovery advice: "How to removing a pending update that is preventing a successful boot" https://social.technet.microsoft.com...w7itprogeneral dism.exe /image:C:\ /cleanup-image /revertpendingactions C:\windows\winsxs\pending.xml The trick is that DISM has to be run at the "real C:" command prompt: https://u.cubeupload.com/pM9fQK.jpg Where clicking on "command prompt" doesn't put me in a "real" C: https://u.cubeupload.com/cN8lpT.jpg So I just want to ask, if that's not the "real C:", should I still attempt the "dism" command to recover the HDD bricked by Microsoft Windows 10 automatic update? If the DISM fails, since the data has to be saved, I have to start fresh with a new hard disk drive and try to recover using TestDisk. http://i.cubeupload.com/WPgdso.jpg |
Ads |
#2
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked byWindows 10 Automatic Update
nik buna wrote:
I may get only one chance to unbrick this system, so I am asking first. https://u.cubeupload.com/luFNrN.jpg In another thread we (Paul, Doomsdrrzej, Wolf K, dogs, etc.) discussed how to recover when Microsoft Windows Update bricked a Win10 Pro boot disk which was working up until the moment of the automatic Windows Update. https://u.cubeupload.com/g3waOf.jpg This thread is just asking the procedure, which "Cameo" did (but who hasn't responded) for using DISM to attempt a recovery of the Microsoft-bricked HDD. http://i.cubeupload.com/2qpmmt.jpg Paul has found the following recovery advice: "How to removing a pending update that is preventing a successful boot" https://social.technet.microsoft.com...w7itprogeneral dism.exe /image:C:\ /cleanup-image /revertpendingactions C:\windows\winsxs\pending.xml The trick is that DISM has to be run at the "real C:" command prompt: https://u.cubeupload.com/pM9fQK.jpg Where clicking on "command prompt" doesn't put me in a "real" C: https://u.cubeupload.com/cN8lpT.jpg So I just want to ask, if that's not the "real C:", should I still attempt the "dism" command to recover the HDD bricked by Microsoft Windows 10 automatic update? If the DISM fails, since the data has to be saved, I have to start fresh with a new hard disk drive and try to recover using TestDisk. http://i.cubeupload.com/WPgdso.jpg Don't panic. Using your Macrium emergency boot CD, make a backup of the drive to an external hard drive. This then leaves you free to try whatever recovery method you want. That's the first step. ******* Your error is this one. This provides some background info. https://answers.microsoft.com/en-us/...18e1ffd?auth=1 ******* However, the context and timing of this event, also provides some evidence. You may be suffering the same issue as one other user here. When you boot the Win10 Installer DVD, select Troubleshooting, there is an option to boot into a Command Prompt window. This uses WinPE. In fact, it's the same WinPE that Macrium uses to support their emergency CD. And the same WinPE used by the Windows 7 Backup subsystem provided in Windows 10 as an emergency boot CD. When WinPE boots, the "OS" is on X: . So the cmd.exe is coming from the X: drive. WinPE is the tiny OS with the maintenace commands like CHKDSK, bootsect, bootrec, dism, sfc, diskpart, and so on. The "target" you're working on, you can establish both during the phase where it asks you which OS partition you're trying to service. (It may ask for a password for that.) Once the Command Prompt appears, you can try dir C: dir D: dir E: ... and see which response "looks" like the OS drive. Now, the last time I did this a few days ago, my OS was on D: . Next, the article you quote, said to look at C:\windows\winsxs\pending.xml If the OS partition was actually D: , then you'd try dir D:\windows\winsxs\pending.xml === prove it exists type D:\windows\winsxs\pending.xml | more === dump to the screen You can see an example here, of me working from the Command Prompt of a Win10 install DVD, and I've satisfied myself that D: is actually the OS partition. When I tried C: (not in the picture), that partition was practically empty, so I know not to try a DISM command against the letter C: . https://s9.postimg.org/th2z2x3hr/sniffing.gif And if everything looks contextually correct (it looked like you had the same problem as other people got recently), you'd try the dism.exe /image:\ /cleanup-image /revertpendingactions When DISM is fed the /image option, it's an "offline" invocation. DISM and SFC support offline work, allowing a person to use a WinPE emergency boot, to effect repairs to an OS partition. In this case, we're trying to roll back an update to D: somehow. I can't tell you any more than that. If you have a backup, and you trust the backup method, you have nothing to worry about. Before I allowed .214 in yesterday on my Win10 Release install, I backed up the OS. Because of the rumblings in the jungle, it seemed like the safe thing to do. I don't do that for all updates, just the ones where people are having trouble. There weren't any outward symptoms at all on my machine... but I'm not discarding the backup quite yet. Maybe in a day or two or three, I'll toss that one. If I could reproduce your situation here, I'd try. But I don't have a "good" AMD processor for the purpose. And it's probably too late now to try anyway. WU has probably been adjusted to not do things that way as of today. Good luck, Paul |
#3
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked byWindows 10 Automatic Update
nik buna wrote:
I may get only one chance to unbrick this system, so I am asking first. https://u.cubeupload.com/luFNrN.jpg In another thread we (Paul, Doomsdrrzej, Wolf K, dogs, etc.) discussed how to recover when Microsoft Windows Update bricked a Win10 Pro boot disk which was working up until the moment of the automatic Windows Update. https://u.cubeupload.com/g3waOf.jpg This thread is just asking the procedure, which "Cameo" did (but who hasn't responded) for using DISM to attempt a recovery of the Microsoft-bricked HDD. http://i.cubeupload.com/2qpmmt.jpg Paul has found the following recovery advice: "How to removing a pending update that is preventing a successful boot" https://social.technet.microsoft.com...w7itprogeneral dism.exe /image:C:\ /cleanup-image /revertpendingactions C:\windows\winsxs\pending.xml The trick is that DISM has to be run at the "real C:" command prompt: https://u.cubeupload.com/pM9fQK.jpg Where clicking on "command prompt" doesn't put me in a "real" C: https://u.cubeupload.com/cN8lpT.jpg So I just want to ask, if that's not the "real C:", should I still attempt the "dism" command to recover the HDD bricked by Microsoft Windows 10 automatic update? If the DISM fails, since the data has to be saved, I have to start fresh with a new hard disk drive and try to recover using TestDisk. http://i.cubeupload.com/WPgdso.jpg If you have no backup of your data, (tisk-tisk), what *I* would do first is download an ISO of Linux installer and create a bootable thumbdrive. Ubuntu is pretty easy and these installers have live sessions in the setup. Live sessions allow you to "Try" without installing. You can use the live session for debugging and rescue. With live session I would try an mount your Windows partition and see if you can access your files. If so it would be a good CYA to backup those files then to another drive or optical media. Doing so would give you at least the peace of mind that you will still have *your* stuff in case your planned rescue goes badly. It maybe just the Windows system files that are corrupted and are preventing you access to the drive and not a "bricked" hard drive. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#4
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
Paul wrote:
When WinPE boots, the "OS" is on X: . So the cmd.exe is coming from the X: drive. WinPE is the tiny OS with the maintenace commands like CHKDSK, bootsect, bootrec, dism, sfc, diskpart, and so on. Thanks for the advice. I had not noticed last time, but looking for C:, I see it's as you said: http://i.cubeupload.com/wl5CyG.jpg The Microsoft failed Windows 10 update booted to an X: drive instead. http://i.cubeupload.com/SDOHZL.jpg The "target" you're working on, you can establish both during the phase where it asks you which OS partition you're trying to service. (It may ask for a password for that.) Once the Command Prompt appears, you can try dir C: dir D: dir E: This was good advice, Paul, and much appreciated. dir A: = The system cannot find the path specified. dir B: = The system cannot find the path specified. dir C: = Directory of C:\ (newline) File Not Found dir D: = this looks like the old C: directory tree dir E: = The device is not ready. etc. Interestingly, this is what results in the C:\ drive that is odd: $Windows.~WS (directory) bootsqm.dat (file of 13,144 size) Recovery.txt (file of 0 size) swsetup (directory) Windows (directory) Windows.old (directory) Windows10Upgrade (directory) and see which response "looks" like the OS drive. Now, the last time I did this a few days ago, my OS was on D: Yes. You are on the mark Paul. The D: directory is the old C: plus it has some extra Windows stuff as shown above. Next, the article you quote, said to look at C:\windows\winsxs\pending.xml That directory is strange in that it's sort of a ghost directory inside of X: and D: at the same time, where when I cd into it, I end up back at X:. dir D:\Windows\WinSxS\*xml Reports only the file migration.xml of 71,685 bytes. The desktop went from Win7 Home Premium OA - Win7 Ultimate Retail - Win10 Pro Retail so that migration may be a result of that (I don't know). If the OS partition was actually D: , then you'd try dir D:\windows\winsxs\pending.xml === prove it exists The only xml is "migration.xml" which is a long line of text stuff. type D:\windows\winsxs\pending.xml | more === dump to the screen You can see an example here, of me working from the Command Prompt of a Win10 install DVD, and I've satisfied myself that D: is actually the OS partition. I can see stuff on D: that makes me agree with you that D: is actually the OS partition on mine also. When I tried C: (not in the picture), that partition was practically empty, so I know not to try a DISM command against the letter C: . I don't even have a C: anymore. Just X: and D: (which is the old C. https://s9.postimg.org/th2z2x3hr/sniffing.gif And if everything looks contextually correct (it looked like you had the same problem as other people got recently), you'd try the dism.exe /image:\ /cleanup-image /revertpendingactions OK. This is what I was mostly asking for assurance on. The disk is 1TB but here's what it said: dism.exe /image:\ /cleanup-image /revertpendingactions Reported the following: Deployment Image Servicing and Management tool Version: 10.0.10589.0 Image Version: 10.0.10586.0 The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024MB. Reverting pending actions from the image... The operation completed. Revert of pending actions will be attempted after the reboot. The operation completed successfully. X:\Windows]WinSxS When DISM is fed the /image option, it's an "offline" invocation. DISM and SFC support offline work, allowing a person to use a WinPE emergency boot, to effect repairs to an OS partition. In this case, we're trying to roll back an update to D: somehow. I can't tell you any more than that. After the reboot, it said the same error as always. It said "preparing automatic repair" And then "diagnosing your PC" And then it failed as before. Do you know of a stronger DISM command? So I think I need a stronger DISM |
#5
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
"Jonathan N. Little" wrote:
It maybe just the Windows system files that are corrupted and are preventing you access to the drive and not a "bricked" hard drive. I have an older Windows 10 ISO DVD disc from last year. Do you think that Windows 10 ISO can "repair" the bricked Windows 10? |
#6
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
"nik buna" wrote in message news I may get only one chance to unbrick this system, so I am asking first. https://u.cubeupload.com/luFNrN.jpg In another thread we (Paul, Doomsdrrzej, Wolf K, dogs, etc.) discussed how to recover when Microsoft Windows Update bricked a Win10 Pro boot disk which was working up until the moment of the automatic Windows Update. https://u.cubeupload.com/g3waOf.jpg This thread is just asking the procedure, which "Cameo" did (but who hasn't responded) for using DISM to attempt a recovery of the Microsoft-bricked HDD. http://i.cubeupload.com/2qpmmt.jpg Paul has found the following recovery advice: "How to removing a pending update that is preventing a successful boot" https://social.technet.microsoft.com...w7itprogeneral dism.exe /image:C:\ /cleanup-image /revertpendingactions C:\windows\winsxs\pending.xml The trick is that DISM has to be run at the "real C:" command prompt: https://u.cubeupload.com/pM9fQK.jpg Where clicking on "command prompt" doesn't put me in a "real" C: https://u.cubeupload.com/cN8lpT.jpg So I just want to ask, if that's not the "real C:", should I still attempt the "dism" command to recover the HDD bricked by Microsoft Windows 10 automatic update? If the DISM fails, since the data has to be saved, I have to start fresh with a new hard disk drive and try to recover using TestDisk. http://i.cubeupload.com/WPgdso.jpg nik, I have recovered 3 systems for a client a bit over a week ago with AMD CPU's that as you say, "got bricked" by the update. While all of the DISM tactics can work, you may be overthinking this problem and not using the built-in recovery tool - specifically recovering from a Restore Point in the Advanced Options System Restore menu. A restore point would have been automatically made before the update and if it's glitched, you have the option to look for other restore points. That assumes of course you had the restore point option on for the C: drive. I did that on all 3 laptops and they were up and running in 15 minutes. If you've tried that already, then you also have the option to Reset the PC and save your files - they won't be touched. But, if you tried all the above do as as Paul stated - make a backup image and/or as Jonathan suggested and make a live CD to manually recover your files and then install a fresh load of Win10. As the screen on the Tesla headed for Mars states "Don't Panic". Bob S. |
#7
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked byWindows 10 Automatic Update
nik buna wrote:
"Jonathan N. Little" wrote: It maybe just the Windows system files that are corrupted and are preventing you access to the drive and not a "bricked" hard drive. I have an older Windows 10 ISO DVD disc from last year. Do you think that Windows 10 ISO can "repair" the bricked Windows 10? The last time you could do a "cold" repair was WinXP. Later OSes, Windows 10 included, need "hot" repair. The OS in need of repair must already be running! Then, you insert the Win10 DVD and execute "setup.exe" off it, to initiate a repair install. Are you sure at this point, what patch caused this ? Is it just a Cumulative, or did the OS upgrade from 15063 to 16299 ? Windows.old should auto-erase itself after 10 days, which makes it a bit weird that there is still a Windows.old on the machine. System Restore points will only exist, if System Restore was turned on and operational before this happened. And if the Windows version changes, Windows 10 likes to turn SR off, so there are no guarantees you have an SR point to work with either. If the Windows.old is intact at this point, and the partition in question really is the OS partition, I wonder if a Revert is possible ? Someone here, Reverted by booting to Safe Mode ("hold Shift Key"). And there was an option to Revert in there (because Windows.old is still there). However, I really think you need to look around, look at dates, look at dates on *log* files and see when and what happened. https://superuser.com/questions/1199...m-command-line If this was really just a "getting the boot to start" issue, I don't think you would have succeeded in getting the "c000021a - The initial session process or system process terminated unexpectedly" as it means the usage of C: has probably started at that point. If you had *two* partitions that looked like OS partitions, that would be more interesting. If this was a dual boot system, with two modern OSes on it, there would be more symptoms possible. If you know for certain there is only the one OS partition, it simplifies the analysis. I don't think the Macrium Reflect emergency CD and its nice "boot repair" option would help here, because I think you're booting, but whatever it is booting into is damaged (somehow). The Windows.old bothers me a bit, because an OS Upgrade has come in recently. But how recently ? Is the Windows.old the root cause, or merely previous baggage ? Paul |
#8
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked byWindows 10 Automatic Update
nik buna wrote:
"Jonathan N. Little" wrote: It maybe just the Windows system files that are corrupted and are preventing you access to the drive and not a "bricked" hard drive. I have an older Windows 10 ISO DVD disc from last year. Do you think that Windows 10 ISO can "repair" the bricked Windows 10? I think you missing what I was saying? 1) Do you love gambling? 2) Is your data not important to you? If either answer is yes than you might like to try anything. However my point was before you do anything, I would try to rescue the data first. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#9
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
Bob_S wrote:
But, if you tried all the above do as as Paul stated - make a backup image and/or as Jonathan suggested and make a live CD to manually recover your files and then install a fresh load of Win10. Thanks for your advice. I did try all that you suggested and what Paul and Jonathan suggested with respect to getting Windows to unbrick itself. I finally removed the HDD and put in a new one and installed Windows 10 on the new hard drive. I still need to recover the data so I'll be doing the other options as I gave up on trying to get Windows 10 to fix itself (even with DISM). |
#10
|
|||
|
|||
Question (for Paul?) on running DISM on hard drive bricked by Windows 10 Automatic Update
"nik buna" wrote in message news Bob_S wrote: But, if you tried all the above do as as Paul stated - make a backup image and/or as Jonathan suggested and make a live CD to manually recover your files and then install a fresh load of Win10. Thanks for your advice. I did try all that you suggested and what Paul and Jonathan suggested with respect to getting Windows to unbrick itself. I finally removed the HDD and put in a new one and installed Windows 10 on the new hard drive. I still need to recover the data so I'll be doing the other options as I gave up on trying to get Windows 10 to fix itself (even with DISM). nik, Now that you have a new drive and you are going to recover your old files - just a reminder so you don't get frustrated and use the old drive for a wheel chock. When you are navigating around the old drive, remember to get to *your* user files via the root directory of C: and look for the "Users" directory and open it up and then open the directory that is *yours* whatever it may be named. Now navigate to "Document", "Downloads" and any other directories where you may have stored files to recover them. Trying to copy files that belong to your account from other than under your directory will result in a lot of "no permission" type errors. I don't know what your hardware setup is but if you can install the old drive in your computer as a secondary drive, that would be one of the best ways to do it. If you can't do it that way, there are SATA to USB cables available that allow you to access the drive but if it's spinning disk hard drive you will need additional power to the hard drive. I won't go into the myriad of ways you can connect to recover the drive but if you need some suggestions let us know your hardware setup and as you know, there's plenty of help here. Bob S. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|