Dell XPS M1530 Startup Repair Loop, Offline SFC does NOT function

writhziden said:

Yes, that should work. Let us know if it spits out any errors with those flags setup.

Writhziden,

First of all, thank you SO much for telling me how to stop a robocopy in its tracks, since I looked all over last night, when the time stretched into hour five, but I couldn't find anywhere on the net that mentioned it to save my life! Thus, I had to let it run while I slept.

Regarding the newly minted command, once I issued it, the program apparently did go to work. But, unlike before, where the files were just zooming across the screen, it appears to now be accessing my donor drive quite a bit. In an effort to gauge which files needs to be copied, I would presume. The list of "EXTRA files/folders" still happens, but if the aborted copy demonstrates anything, it should eventually go into copying the new files and folders.

*Crosses fingers and toes*

When I tested it on my machine, it found extra directories, but it still copied over the files, so that should work fine.

I also noticed some pre-processing when I used the MT command, so I think that is normal.

writhziden said:

When I tested it on my machine, it found extra directories, but it still copied over the files, so that should work fine.

I also noticed some pre-processing when I used the MT command, so I think that is normal.

Slight Update: As this post is being written, it is officially more than 11 hours since I've initiated the process, and it's still fraking going. I thought about canceling it after I got home from work, but being that it already had been six hours or so, I just thought that I'd let it run its course. After all, if I didn't, those six hours would a complete waste of time, electricity, heat, and emotional potential. Even if this process doesn't end up working, at least we will have learned something from it.

Regarding the absurd length of time required, as far as I can tell, is due to your /IS and /IT tags, mister. Based on what I can see from my USB external drive's behavior, it almost seems as if Robocopy is doing a literal bit to bit detailed examination, where it evaluates each bit in the file to see if any is different before it induce an overwrite. If that's the case, then if it doesn't work, we can at least state for sure that the problems resides in one of the non-essential files that did not get replaced by the move. After all, everything else is new.

Meh. I'll go back to waiting, nervously mumbling to myself, and practicing my rendition of "It's alive! IT'S ALLIIIIIVEEEEEEEE!!!!Eleventy-One!!!" God knows that if it doesn't work, my tears won't need a practice to do a good job.

Odd that it is taking so long. In the test run I did copying Windows over with robocopy with the same flags, it took about an hour. I have a clean install that I am copying over to my current install to see if it causes any strange behavior; as I said, that took about an hour. I have to do it again because my registry backup was not complete, so when I copied things over, the registry was overwritten, and my software would not run. Windows complained that "That can only be done with software that is installed" or something of that nature. I am going to do a full registry backup to simulate what you have and see if it works better.

I used /mt:119, but I still wouldn't expect that much of a difference in time.

Writhziden,

Okay. Is it just me, or are the forums a little funky and crazy tonight? For some reason, I couldn't get in for the last two to three hours, and now that I've gotten in, our conversation in this thread looks like it's all out of chronological whack. Did we piss off someone in Anonymous or something? Regardless, I was glad that you send me your reply when you did, since I think that it literally made it under the wire and got to me before the site went nuts. Thus, I've been working on getting the Franken-OS imaged, just in case that things did go pop-goes-the-weasel on us. One thing that I've noticed is that regardless of imaging, copying, or whatever, something about this computer's OS makes it so that it does it much slower than other systems. For example, when I first cloned the drive, when it was broken to hell, it literally only took 18 minutes. However, this time, it took approximately two hours!

As for my efforts in restoring everything to fully functional shape, I think that after the imaging, I am going to uninstall SP1, do the repair install as you recommended, then re-update everything once again. As far as I'm concerned, if that doesn't fixes it, it's no longer my fault. After all, I think we can both agree that I've done pretty much everything I can, up to and including that unlikely and improbable, for my uncle and cousin. Thus, I'm not going to waste any more time on this thing. Here's hoping that whoever uses this thing will take good care of it.

Meh. I'll try to write more once I get the repair install underway. Also, I'm curious to what you think about the article. Is it something that you can is doable? Or, is making a Franken-OS too dangerous for the typical user to try?

writhziden said:

I think the methods used in this thread (which sadly are now missing due to the server crashing) should only be used in very special cases such as yours. We get a lot of questions asking "Would it be possible to move all my programs and user files over to a new computer by just transferring all the files?" We have answered that question in this thread and pretty much confirmed what we usually say: It would be possible, but not recommended since things probably will not run as expected afterward and you may end up with more trouble than its worth.

Now, you did not have a choice in the matter, so patching things back together was really the only option. For that, I am very glad that the steps worked.

• Create a system image or clone of the system no longer working.
• Clean Install Windows 7
• Install all Windows updates that were installed on the broken system and install all system drivers.
• Create a system image or clone of the updated, working install.
• Restore the system image of the broken system.
• Use a Windows 7 repair disc, a Windows 7 installation disc, or a Macrium Reflect Windows disc to robocopy all files from the Windows directory on the working system within the system image or clone to the Windows directory on the now restored broken system.
• Copy the entire [drive letter of old broken system copy]:\Windows\System32\config directory from the broken system's clone or system image to the now broken/patched [drive letter of current system]:\Windows\System32\config or copy just the registry files.
• See if Windows starts and programs run, and if so, create another system image of the current system.
• Repair Install Windows 7.

Writhziden,

I'll be honest in stating that I am not, nor will I ever, support the notion that every one who has been lax in backing up their shiznit to try Frankenstein their drives when disaster strikes; you and I know for certain that there are plenty of little issues that is still wrong with this machine, and frankly, I'm reaching the point of frustration induced apathy. However, I will be also say that, once the biggest issues are taken care of, the Franken-OS is rather stable and serviceable for the time being. Granted, it could explode into a million pieces tomorrow, but... this is a Microsoft product. It could potentially do that regardless the next time they release an update.

Regarding the final repair install step, I'll be honest that I didn't do it, and I'm on the fence whether or not I'm going to do so, partly because I don't have a Windows 7 SP1 disc with which to do the repair install with (I couldn't get rid of SP1, since I'd done a disk cleanup whilst the servers were down, so I didn't know that removing that file would prevent the removal of SP1. D'oh!), and partly because I realized how much work the repair install will ruin.

Just curious, would the repair install be so germane to the stability and such that it is absolutely required? If so, I'll go ahead and download a SP1 installation ISO from MSDN. However, faced with the notion of needing to once again weed things out of the Windows.old folder, or installing the old Dell supplied Vista drivers does not thrill me in the least, especially since I'm not entirely sure if they were/are part of the problem, and I find myself wondering at exactly what will be replaced and what settings or such will I lose. What is your opinion?

As I said, I would create a system image of the current system first.

The repair install should not affect any of the programs or user files currently on the system. I cannot guarantee it given the amount of stitching together that has been done, but I would still be surprised if it made matters worse. It should make the system a lot more stable and allow things to work more reliably. If you have the time to download the DVD with SP1 integrated and burn the ISO, do the repair install, and revert to the saved image (I'm guessing 4-5 hours for the whole process if things go wrong, 2-3 hours if it goes smoothly), then go through the process.

If you do not have that time and the computer needs to be returned soon, then leave it as is and recommend to the owner to make a system image and do a repair install. You can refer the person to these forums and someone on here can walk the person through the process in easy steps.

writhziden said:

As I said, I would create a system image of the current system first.

The repair install should not affect any of the programs or user files currently on the system. I cannot guarantee it given the amount of stitching together that has been done, but I would still be surprised if it made matters worse. It should make the system a lot more stable and allow things to work more reliably. If you have the time to download the DVD with SP1 integrated and burn the ISO, do the repair install, and revert to the saved image (I'm guessing 4-5 hours for the whole process if things go wrong, 2-3 hours if it goes smoothly), then go through the process.

If you do not have that time and the computer needs to be returned soon, then leave it as is and recommend to the owner to make a system image and do a repair install. You can refer the person to these forums and someone on here can walk the person through the process in easy steps.

Meh. Fair enough. Apparently my uncle doesn't have time to meet up until Sunday, so I suppose I have some more time to tinker with this, even if I am having frustrating induced apathy and "real artists ship/ done is better than perfect" problems. I've already made an image of the Franken-OS, so that's not going to be an issue. Mostly, I'm just sick of this machine, and even though I am totally proud that I lewis-and-clarked my way through that patch of Microsoft Wilderness, I kind of just want to be done with this piece of junk.

Just wondering, do you have a guide on what files I should move back from the repair install generated "Windows.old" folder? I know that I may need to move my registry back, but that's about it. Also, before I forget, how do you guys get your posts? I'm not saying that I'd stick around all the time like a bar fly or something, but it seems pretty fun to come hang out and help people few times a week. =)

I just go through and look for problems I am familiar with and know how to help with. Then e-mails show up in my e-mail box notifying me when people respond.

For the repair install, you won't have a Windows.old folder if you follow the instructions to Repair Install Windows 7. It does an in place upgrade that leaves all non-Windows files and software in place and ready to use. That is the beauty of it. :)