+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Computing (https://hackforums.net/forumdisplay.php?fid=88)
+---- Forum: Microsoft Windows (https://hackforums.net/forumdisplay.php?fid=347)
+---- Thread: [URGENT] Window 7 completely corrupted, paying to get this fix (/showthread.php?tid=5427685)
[URGENT] Window 7 completely corrupted, paying to get this fix - Louis C.K. - Oct 8, 2016
It started off with me extending the partition with partition wizard, trying to extend my c with unallocated space, it ask for a restart and my system is completely corrupted. Trying to use win7 startup repair and my c isn't even listed on the driver list. Unknown on (unknown) Local Disk. Tried the bootrec, bootrec /scanos doesn't work, can someone help me fix this?
* - datguy.dev - Oct 9, 2016
Do you know if the previous disk layout was MBR or GPT? Can you use diskpart to see if the partitions are intact?
Try using the bootrec /fixmbr > bootrec /fixboot > then bootrec /rebuildbcd. Reboot.
* - Louis C.K. - Oct 9, 2016
(Oct 9, 2016 12:02 AM)datguy.dev Wrote: Do you know if the previous disk layout was MBR or GPT? Can you use diskpart to see if the partitions are intact?
Try using the bootrec /fixmbr > bootrec /fixboot > then bootrec /rebuildbcd. Reboot.
I believe is was MBR, I tried the bootec commands and none work, the main issue now is that it can't locate my C drive is where the OS is install on
* - datguy.dev - Oct 9, 2016
(Oct 9, 2016 10:09 AM)Steve Stifler Wrote: I believe is was MBR, I tried the bootec commands and none work, the main issue now is that it can't locate my C drive is where the OS is install on
The MBR contains partitioning scheme information. Without fixing it, you'll never get your old C volume back. I'm afraid you've lost the old information and should go into the data recovery.
These issues are difficult to diagnose on a forums without all the information. You should explain the output of the commands and meta information about the disk. You can also clone the drive and take it to a shop to see if they can manage.
* - Louis C.K. - Oct 9, 2016
(Oct 9, 2016 12:12 PM)datguy.dev Wrote: The MBR contains partitioning scheme information. Without fixing it, you'll never get your old C volume back. I'm afraid you've lost the old information and should go into the data recovery.
These issues are difficult to diagnose on a forums without all the information. You should explain the output of the commands and meta information about the disk. You can also clone the drive and take it to a shop to see if they can manage.
ok, I will just fresh install win7 then, problem is I will have my C drive where the OS is install on and a drive of unallocated space, I am trying to extend my C with the unallocated space, I can't use partition manager in win7 to this so I have to use a third party sw call minitool partition wizard, but if I do so I think my C will corrupt again. What do you think is making the system corrupt? Does manual restore point fix all BSOD?
* - datguy.dev - Oct 9, 2016
(Oct 9, 2016 12:47 PM)Steve Stifler Wrote: ok, I will just fresh install win7 then, problem is I will have my C drive where the OS is install on and a drive of unallocated space, I am trying to extend my C with the unallocated space, I can't use partition manager in win7 to this so I have to use a third party sw call minitool partition wizard, but if I do so I think my C will corrupt again. What do you think is making the system corrupt? Does manual restore point fix all BSOD?
Even if you're doing everything right, there will always be a small chance of breaking the install when shrinking or extending partitions. It comes with the territory.
Traditionally, you cannot span a Windows installation across multiple disks. https://technet.microsoft.com/en-us/library/cc753058(v=ws.11).aspx You can extend a dynamic disk on the same drive though. That is probably the source of your corruption. Windows was telling you not to do so. :D I've heard of people doing so with hardware RAID, but never tried it myself.
BSOD is another topic. Can't tell without the dumps and stop errors.