Hello All,
I am a new member to Sysnative and I am pretty much a newbie on this PC problem solving area and am in need of some help if possible. I have Win 7 Home Premium SP1 64-bit. The PC was scanned for any Malware or Virus' and there are none.
I tried to do a clone on 6-7-15 and it failed. After it failed, I found that three partitions on the disk I was cloning to "GQ0T" had been completely erased. The drive had been cloned before successfully last month on 5-11-15 from the same internal drive "ED5S". The hard drive I was cloning from "ED5S" , had (C:) drive letter changed to (E:). Other partition letters on "GQ0T" were changed as well! This is NOT supposed to happen! As a result, the hard drive "ED5S" is no longer bootable! I suspect the reason for the clone failure on 6-7-15 was recent MS updates that were corrupted and prevented reading to the VSS service. The MS updates were: KB3022345 and KB3068708. However, a clone failure should not cause the problems it did! Erasing partitions on the drive being cloned to "GQ0T" and changing drive letters on the drive "ED5S" being cloned. Fortunately none of the drive's information on "ED5S" was deleted but the drive is not usable!
I used another hard drive "MR3T" that had been cloned at an earlier date and swapped out the corrupt drive "ED5S" that will not boot. I then attached "ED5S" and was then able to see that all the partitions were intact and it appears that no folders/files were deleted and the total GB used was still the same but the drive letters had been changed. The O/S (C:) drive letter was changed to (E:). The (E) is for my CD/ROM. Naturally Windows can't boot from an empty (E:) drive. Anyway, I did a SFC /SCANNOW on the corrupt drive "ED5S" and the scan picked up two corrupt files: KB3022345 ”telemetry.ASM-WindowsDefault.json” and "utc.app.json" . KB3068708 has these same issues. SFC /SCANNOW could not fix these. I deleted the updates using elevated command prompt and this program (SFCFix.zip). Inaddition, I had previously run chkdsk C: /F /R for disk "ED5S" and chkdsk replaced two bad clusters.
I also ran F-8 to repair startup on "ED5S" which found the (C) drive misnamed as (E). Startup repair reported fixing this but when I installed the drive back in the PC it still would not boot. The (C) drive still shows as (E) when I use F-10 to check the boot order. I'm at a loss as to how to proceed from here to fix the boot menu and drive letter reversal problem. :huh: Any help or advise provided would be greatly appreciated.
Thank you, Dave
