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
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
i need help. Badly.
Machine won't boot after an automatic Windows 10 automatic update. It's definitely Windows update which screwed up the file system. It won't even mount via an SATA adaptor on another machine. Pics below but the question is what can I do to get my filesystem back? 1. Reset this PC http://i.cubeupload.com/2qpmmt.jpg 2. Scanning & repairing http://i.cubeupload.com/iSgdCX.jpg 3. Startup repair http://i.cubeupload.com/g3waOf.jpg 4. Go back to previous build http://i.cubeupload.com/o5jbt1.jpg 5. Reset thi PC again http://i.cubeupload.com/RTVm65.jpg 6. Reset options http://i.cubeupload.com/BQrRDY.jpg 7. Resetting this PC http://i.cubeupload.com/G6wbuu.jpg 8. There was a problem http://i.cubeupload.com/YLSw2s.jpg 9. Error code 0xc000021a http://i.cubeupload.com/luFNrN.jpg 10. OxFFFFC001CB4CEE50 http://i.cubeupload.com/AIeI0X.jpg 11. Startup settings http://i.cubeupload.com/cN8lpT.jpg 12. I tried every single one http://i.cubeupload.com/Wb4AuW.jpg 13. I tried all attempting repairs http://i.cubeupload.com/dqyHQf.jpg 14. I tried all advanced options http://i.cubeupload.com/pM9fQK.jpg 15. I attached the sata adapter http://i.cubeupload.com/z17IFe.jpg 16. The file system is corrupt http://i.cubeupload.com/lbeTE3.jpg I don't understand what the error code is trying to say since it's Microsoft who caused this problem so they should know more than this. https://docs.microsoft.com/en-us/win...ess-terminated How can I get my filesystem back? (there no recent backup). |
Ads |
#2
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
On 31/01/2018 22:05, nik buna wrote:
Microsoft who caused this problem so they should know more than this. Please repost your question without blaming Microsoft. Microsoft didn't cause any problems for you; You caused the problem yourself because you are so stupid with brain smaller than a smallest bird available on this planet. We don't like helping people of low intelligence so **** off. Next time don't use a silly name nik buna because there is no name like that on this planet. You are a known pedo here so bugger off. -- With over 600 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#3
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
nik buna wrote:
i need help. Badly. Machine won't boot after an automatic Windows 10 automatic update. It's definitely Windows update which screwed up the file system. It won't even mount via an SATA adaptor on another machine. Pics below but the question is what can I do to get my filesystem back? 1. Reset this PC http://i.cubeupload.com/2qpmmt.jpg 2. Scanning & repairing http://i.cubeupload.com/iSgdCX.jpg 3. Startup repair http://i.cubeupload.com/g3waOf.jpg 4. Go back to previous build http://i.cubeupload.com/o5jbt1.jpg 5. Reset thi PC again http://i.cubeupload.com/RTVm65.jpg 6. Reset options http://i.cubeupload.com/BQrRDY.jpg 7. Resetting this PC http://i.cubeupload.com/G6wbuu.jpg 8. There was a problem http://i.cubeupload.com/YLSw2s.jpg 9. Error code 0xc000021a http://i.cubeupload.com/luFNrN.jpg 10. OxFFFFC001CB4CEE50 http://i.cubeupload.com/AIeI0X.jpg 11. Startup settings http://i.cubeupload.com/cN8lpT.jpg 12. I tried every single one http://i.cubeupload.com/Wb4AuW.jpg 13. I tried all attempting repairs http://i.cubeupload.com/dqyHQf.jpg 14. I tried all advanced options http://i.cubeupload.com/pM9fQK.jpg 15. I attached the sata adapter http://i.cubeupload.com/z17IFe.jpg 16. The file system is corrupt http://i.cubeupload.com/lbeTE3.jpg I don't understand what the error code is trying to say since it's Microsoft who caused this problem so they should know more than this. https://docs.microsoft.com/en-us/win...ess-terminated How can I get my filesystem back? (there no recent backup). You need an environment with TestDisk on it. https://www.cgsecurity.org/wiki/TestDisk You can bring the damaged disk over to your working PC, and run TestDisk against it from that machine. You can boot a Linux LiveCD on the affected machine and run TestDisk from there. You might not even have to install a TestTisk package in Ubuntu to get it, as an example. TestDisk can do two things. 1) Scan for partitions. That's not the function we need in this case, so you can stop it at some point. Generally, the partition computing function isn't that robust, and it requires "judgment" before using the results of any scan. 2) The TestDisk program can traverse the file system and list the files. If it can do that, this implies the file system is recoverable. At that point, we don't know *how* to recover it, but we know *it isn't toast*. There's no point in doing file-by-file recovery at this point, as it appears you're expecting this OS to be revived and usable. So I'm not going to go off on a trip down that path just yet. If you have third-party AV software, it might be nothing more than some quarantined system files (like maybe the kernel file or something). Once you've had a poke at it with some different tools, you might have a better idea whether it's a minor problem, or a major meltdown. HTH, Paul |
#4
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
Paul wrote:
You need an environment with TestDisk on it. Thank you for that advice of testdisk as I "think" the OS is still good because I get the blue screen from Microsoft which *knows* what to do (it just fails at everything it tries). You can bring the damaged disk over to your working PC, and run TestDisk against it from that machine. The funny thing is I "thought" the SATA hardware adapter would just "mount" the HDD as a USB disc, but it doesn't recognize the "filesystem", so, the Microsoft Update definitely did something to kill the file system - but what? You can boot a Linux LiveCD on the affected machine and run TestDisk from there. You might not even have to install a TestTisk package in Ubuntu to get it, as an example. Thanks for that idea, which sounds good especially since I'm only borrowing a computer right now as mine is dead from the Microsoft Update. My original plan was: 1) Borrow a computer with a large HDD to copy the data over for safekeeping 2) Then format the HDD and reinstall Windows 10 and bring the data back But what I might do, based on your suggestion, is: 1) Buy a SATA HDD (I could always use it) to put Windows on that new HDD 2) Then install a dual boot of Windows/Ubuntu to troubleshoot further I don't need the data at this moment as much as I need a machine that isn't borrowed so I think I'll go out and buy a HDD (which I haven't bought in years so I'm not sure what's "common" nowadays). TestDisk can do two things. 1) Scan for partitions. That's not the function we need in this case, so you can stop it at some point. Generally, the partition computing function isn't that robust, and it requires "judgment" before using the results of any scan. I think the original HDD was a single 1TB partition, if that's possible. I don't remember seeing any other HDD drives on it. 2) The TestDisk program can traverse the file system and list the files. If it can do that, this implies the file system is recoverable. At that point, we don't know *how* to recover it, but we know *it isn't toast*. Thanks for that advice. I can't imagine that the file system is toast, just yet, as the HDD didn't crash AFAIK. It's just that the Microsoft Update killed "something" where the update was having problems before it wiped out the system. Basically the update was failing over and over again, which is due to me, almost certainly, turning stuff off - where Microsoft doesn't actually test their updates against a non-standard system. I've seen this "kind" of problem for years, where Microsoft Updates only work well on a "standard" system, due to programming assumptions that are dead wrong on a system with the bells and whistles tweaked (e.g., winaero). There's no point in doing file-by-file recovery at this point, as it appears you're expecting this OS to be revived and usable. So I'm not going to go off on a trip down that path just yet. Interesting observation, as my original plan was to copy my data directory (which is all I care about) if I could mount the SATA HDD, but my second plan was to run Recuva if I couldn't save the data in its entirety. It's unlikely any of the data was overwritten as the Microsoft Update killed it suddenly so there was no use of the file system after the reboot after the update so the files are there - the file system is the problem. Microsoft Update screwed up "something" in the file system - but what? If you have third-party AV software, it might be nothing more than some quarantined system files (like maybe the kernel file or something). Once you've had a poke at it with some different tools, you might have a better idea whether it's a minor problem, or a major meltdown. I don't have an AV running on that computer but it's a great idea that something could have blocked the Microsot Update from working. I think the most plausible rationale is that Microsoft doesn't expect people to modify the system (Winaero for example), and hence the programmers assumed somethin which wasn't the case. The only question now is how to recover the data, all of which is in a single directory - but I have to mount the file system before I can access that single directory (which is probably 10GB or so in data size). I think, for now, I'll do this (how does this sound?). 1) I'll give up on the borrowed Win10 desktop (albeit, it is *fast*!) 2) I'll buy a new SATA HDD for my Win7-Win10 older desktop 3) I'll put Win10 on that HDD & then Ubuntu (I think Windows has to be 1st) 4) That gets me off the borrowed machine and back onto mine At that point, I'll run the Ubuntu/Windows testdisc process. If that fails, I'll try Recuva. Anything else? |
#5
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
nik buna wrote:
Paul wrote: You need an environment with TestDisk on it. Thank you for that advice of testdisk as I "think" the OS is still good because I get the blue screen from Microsoft which *knows* what to do (it just fails at everything it tries). You can bring the damaged disk over to your working PC, and run TestDisk against it from that machine. The funny thing is I "thought" the SATA hardware adapter would just "mount" the HDD as a USB disc, but it doesn't recognize the "filesystem", so, the Microsoft Update definitely did something to kill the file system - but what? You can boot a Linux LiveCD on the affected machine and run TestDisk from there. You might not even have to install a TestTisk package in Ubuntu to get it, as an example. Thanks for that idea, which sounds good especially since I'm only borrowing a computer right now as mine is dead from the Microsoft Update. My original plan was: 1) Borrow a computer with a large HDD to copy the data over for safekeeping 2) Then format the HDD and reinstall Windows 10 and bring the data back But what I might do, based on your suggestion, is: 1) Buy a SATA HDD (I could always use it) to put Windows on that new HDD 2) Then install a dual boot of Windows/Ubuntu to troubleshoot further I don't need the data at this moment as much as I need a machine that isn't borrowed so I think I'll go out and buy a HDD (which I haven't bought in years so I'm not sure what's "common" nowadays). TestDisk can do two things. 1) Scan for partitions. That's not the function we need in this case, so you can stop it at some point. Generally, the partition computing function isn't that robust, and it requires "judgment" before using the results of any scan. I think the original HDD was a single 1TB partition, if that's possible. I don't remember seeing any other HDD drives on it. 2) The TestDisk program can traverse the file system and list the files. If it can do that, this implies the file system is recoverable. At that point, we don't know *how* to recover it, but we know *it isn't toast*. Thanks for that advice. I can't imagine that the file system is toast, just yet, as the HDD didn't crash AFAIK. It's just that the Microsoft Update killed "something" where the update was having problems before it wiped out the system. Basically the update was failing over and over again, which is due to me, almost certainly, turning stuff off - where Microsoft doesn't actually test their updates against a non-standard system. I've seen this "kind" of problem for years, where Microsoft Updates only work well on a "standard" system, due to programming assumptions that are dead wrong on a system with the bells and whistles tweaked (e.g., winaero). There's no point in doing file-by-file recovery at this point, as it appears you're expecting this OS to be revived and usable. So I'm not going to go off on a trip down that path just yet. Interesting observation, as my original plan was to copy my data directory (which is all I care about) if I could mount the SATA HDD, but my second plan was to run Recuva if I couldn't save the data in its entirety. It's unlikely any of the data was overwritten as the Microsoft Update killed it suddenly so there was no use of the file system after the reboot after the update so the files are there - the file system is the problem. Microsoft Update screwed up "something" in the file system - but what? If you have third-party AV software, it might be nothing more than some quarantined system files (like maybe the kernel file or something). Once you've had a poke at it with some different tools, you might have a better idea whether it's a minor problem, or a major meltdown. I don't have an AV running on that computer but it's a great idea that something could have blocked the Microsot Update from working. I think the most plausible rationale is that Microsoft doesn't expect people to modify the system (Winaero for example), and hence the programmers assumed somethin which wasn't the case. The only question now is how to recover the data, all of which is in a single directory - but I have to mount the file system before I can access that single directory (which is probably 10GB or so in data size). I think, for now, I'll do this (how does this sound?). 1) I'll give up on the borrowed Win10 desktop (albeit, it is *fast*!) 2) I'll buy a new SATA HDD for my Win7-Win10 older desktop 3) I'll put Win10 on that HDD & then Ubuntu (I think Windows has to be 1st) 4) That gets me off the borrowed machine and back onto mine At that point, I'll run the Ubuntu/Windows testdisc process. If that fails, I'll try Recuva. Anything else? You might want to review the known info for the update in question. Someone in the Win7 group had a Turion based machine bricked by a Win7 update that had issues with certain AMD processors. And the person ("Cameo") managed to figure out how to do an offline removal of the defective update. Impressive :-) This is the text from the posting. The tools that Cameo used to fix this we "I was able to use the original Win7 install DVD in Repair Mode that gave my DOS command window where I entered: DISM /image:c:\ /cleanup-image /revertpendingactions Because the corrupt package was not installed com completely I was able to use this shorter DISM command instead of the longer DISM /image:c:\ /remove-package /packagename: etc. command. After the restart my Win7 booted up normally and the update history shows that KB4056894 installation failed: " And even though that's Windows 7, that's the Spectre/Meltdown set. There were about six sequential patches, in the '892 range, and they're for different OSes. It could be that the Win10 equivalent of that update, got your AMD??? machine. Not all AMD are affected, but a few older ones were. http://al.howardknight.net/msgid.cgi...nt-email.me%3E Paul |
#6
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
Paul wrote:
Not all AMD are affected, but a few older ones were. This Win10 PC has the AMD 785G chipset. It's an HP Pavilion P6230 with the Aloe motherboard (H-RS880-uATX). You'd think Microsoft would test their updates before sending them out and bricking everyone's system. |
#7
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
Paul wrote:
"I was able to use the original Win7 install DVD in Repair Mode that gave my DOS command window where I entered: DISM /image:c:\ /cleanup-image /revertpendingactions Because the corrupt package was not installed com completely I was able to use this shorter DISM command instead of the longer DISM /image:c:\ /remove-package /packagename: etc. command. I should have mentioned that the ONE THING that worked was to boot to the "DOS" command line, where it put me at the command line *inside* of the Windows directory (I think it was c:\windows\system32\) but it wasn't a "real" Windows. I wasn't sure WHAT it was, as it didn't do much with a dir of C:\ so I gave up on that command line. But if one of those commands above will work, I can try it. Do you recommend I put the hard drive back in the Win10 desktop, and boot to the command line, and run something? |
#8
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
Paul wrote:
It could be that the Win10 equivalent of that update, got your AMD??? machine. Not all AMD are affected, but a few older ones were. I forgot to mention that the boot to command prompt in safe mode worked. https://u.cubeupload.com/pM9fQK.jpg Do you think I can run a command in this safe mode prompt that will revert back to the working Windows 10 prior to the Spectre update? |
#9
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
On Thu, 01 Feb 2018 16:04:43 -0500, Paul wrote:
nik buna wrote: Paul wrote: .. because I get the blue screen from Microsoft which *knows* what to do .. the Microsoft Update definitely did something to kill the file system - but what? .. borrowing a computer right now as mine is dead from the Microsoft Update. .. It's just that the Microsoft Update killed "something" where the update was having problems before it wiped out the system. .. Basically the update was failing over and over again, .. It's unlikely any of the data was overwritten as the Microsoft Update killed it suddenly .. Microsoft Update screwed up "something" in the file system - but what? .. Someone in the Win7 group had a Turion based machine bricked by a Win7 update .. After the restart my Win7 booted up normally and the update history shows that KB4056894 installation failed: Oh man, the useless "Good Guy" is blowing a gasket now. And he can't call Paul a stupid birdbrain. This is just too funny. |
#10
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
nik buna wrote:
Paul wrote: It could be that the Win10 equivalent of that update, got your AMD??? machine. Not all AMD are affected, but a few older ones were. I forgot to mention that the boot to command prompt in safe mode worked. https://u.cubeupload.com/pM9fQK.jpg Do you think I can run a command in this safe mode prompt that will revert back to the working Windows 10 prior to the Spectre update? That screen is presented from WinPE while the system is booting. I don't think you're actually in Safe Mode yet when you're there. When you run Command Prompt from within WinPE, you're effectively servicing the OS "offline". The WinPE OS drive is "X:\" . C: may or may not be C: . The drive lettering doesn't have to be consistent, and it pays to verify which disk is which. To do offline servicing of an OS, you need some way to tell what just came in and what just broke. I can't tell from the symptoms right now, just what came in. One spec I can see for P6230 says it uses an AMD Phenom II processor. But some of the popular HP models, they actually use a number of different processors and motherboards. Some even have both Intel and AMD solutions available for the same chassis. That's why I have to be careful to not jump to any conclusions. ******* https://www.tomsguide.com/us/meltdow...ews-26389.html https://support.microsoft.com/en-ie/...-based-devices https://support.microsoft.com/en-us/...-screen-errors Stop error doesn't let you get to the desktop. Choose an option screen, select Troubleshoot Advanced options System Restore. This option reverts your PC to an earlier point, called a system restore point. Restore points are created when you install a new app, driver, update, or when you create a system restore point manually. Choose a restore point created before the error occurred. But that will only work if Restore Points were enabled. Windows 10 has a tendency to turn those off when a new release of OS comes out, requiring the user to turn it back on again. That means, in an emergency, there's probably no restore point available. When a new OS comes in, logically there are no restore points stored in it. Restore Points only accumulate after that point, and only if System Restore is turned on. This is what Cameo did. The only mystery part for me, is knowing what state the OS is in at a moment. "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 When you boot to the Command Prompt (upper right in your picture)... https://u.cubeupload.com/pM9fQK.jpg you would start by dir C: and see if C: looks like the OS partition in that environment or not. Normally it would be, but if you were working on a dual boot, there could be two OS partitions, and one of them could be D: . When you specify the /image option, you have to make sure it's really the borked OS that you're pointed at. The second item from that article, suggested there is a pending.xml file in WinSXS. Even if there is one, I doubt there will be sufficient plain English in there to explain what update is jammed. That subsystem tends to use GUIDs and not anything a human could use directly. You can try the "revertpendingactions", because if nothing is Pending and the damage is done, the command will error out, and you'll be no worse off. ******* Now, if an update was fully installed, nothing was pending, you'd have to look for a way to remove it. https://docs.microsoft.com/en-us/win...ine-using-dism DISM /Image:C:\test\offline /Remove-Package /PackageName:Microsoft.Windows.Calc.Demo~6595b6144c cf1df~x86~en~1.0.0.0 First of all, DISM is used by IT people for building images for deployment. And that's the context of that example. To use that method, you'd need a PackageName, and that means finding a log entry with the name in it or something. There are commands when the OS is *online* to list such things (wmic???), but when the OS is *offline*, your options regarding querying stuff are strictly limited. In this example, they use "wusa" to remove an update, but this is an online example, not offline like you are right now. https://www.ghacks.net/2014/08/18/ho...ndows-updates/ # Administrator command prompt... wusa /uninstall /kb:1234567 That's why at this point, a blind "revertpendingactions" is your only practical option. You can't expect CBS.log to have information a human can actually use for this. Paul |
#11
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
On Thu, 1 Feb 2018 20:05:29 -0800, nik buna
wrote: Paul wrote: Not all AMD are affected, but a few older ones were. This Win10 PC has the AMD 785G chipset. It's an HP Pavilion P6230 with the Aloe motherboard (H-RS880-uATX). You'd think Microsoft would test their updates before sending them out and bricking everyone's system. That's a crazy idea which doesn't benefit Microsoft in any way. The only acceptable thing for you to do is accept the fact that your system is bricked and buy a new one, preferably one of the Surface products. |
#12
|
|||
|
|||
Win10 update this week corrupted my file system (need help)
Doomsdrzej wrote:
On Thu, 1 Feb 2018 20:05:29 -0800, nik buna wrote: Paul wrote: Not all AMD are affected, but a few older ones were. This Win10 PC has the AMD 785G chipset. It's an HP Pavilion P6230 with the Aloe motherboard (H-RS880-uATX). You'd think Microsoft would test their updates before sending them out and bricking everyone's system. That's a crazy idea which doesn't benefit Microsoft in any way. The only acceptable thing for you to do is accept the fact that your system is bricked and buy a new one, preferably one of the Surface products. === gah!!! Have you seen the trail of "support slime" behind those ? Real computer companies do a better job of curating drivers and other stuff, to make their products work. The life of a Surface owner is hardly simple. Maybe if you fly 747s for a living, you're used to all the knobs and levers that'll need adjustment. And to top it off, Windows 10 S is launched on those, when no other company wants to bother. It's like putting a $0.10 plastic hood ornament on your Bentley. They should at least provide Windows 10 Pro right away. And leave a disc with Windows 10 S on it in the box, for those who really wanted it (a couple hundred thousand polycarbonate discs to be thrown into the landfill, win). I can see a $0.10 OS on a Chromebook, but the Surface products cost many times what a Chromebook would cost. The price puts them in an entirely different tier. Microsoft: 1) Fit and finish failure. "My accelerometer doesn't work." 2) Poor product placement. Windows 10 S on $1000+ computers ? Gah!!! Next they'll be putting Linux on them :-) Or FreeDOS or something. Just what someone who has spent $1000 on a computer expects. Example: https://www.computerworld.com/articl...-software.html "The Surface Pro 3 had 10 firmware/driver updates in its first six months, with a dozen more since then. There was the Simplo batterygate fiasco which triggered a class action lawsuit, a second battery problem, and a bewildering array of freezes, blue screens, and other anomalous behavior." Now, *that's* the computer company I want to do business with. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|