Main Forum > General Computer Support
Windows 7 Ult 64 bit trapped by BSD and can not get out.
FreeCat:
OK STATUS IS: I have created a bootable W7 DVD disc from the Speccry program. Thanks. Feeling very good so far. Will report more shortly.
FreeCat:
Hi - I have come to a quandary:
I know I have to do the repair install based on what you said:
"Before you perform the repair install, create an image onto external media and run Windows Repair in Safe Mode and then see if a sfc /scannow still reports it cannot repair that MSDTC Log, as that could have been the result of those infections.
It's probably prudent to create a system image now before you eventually go ahead with those updates and then you'll have something to fall back on."
But, I installed a new AOMEI Backerupper but it gets a 4xxx error that I sent to them. They said, uninstall reboot install and reboot, which I am in the process of doing. But, after that I am not sure how to perform the repair install. I looked back at the log and can not find that.
So, after i do the image backup, exactly what do I do with the system disc to get system back to normal so I can put on those updates?
How do I do that? Thanks in advance.
Boggin:
If you can't get AOMEI to work then you can use Windows own Create a system image.
When you have created a system image/backup and run Windows Repair in Safe Mode with Networking, run another sfc /scannow to see if it still reports it is unable to repair that file.
If that is the case then you will need to proceed with the repair install.
Prior to doing a repair install it is advised that you back up your drivers folders onto something like an USB stick.
They can be found at C:\Windows\System32 and there are three of them and then you can drag and drop them back in after the install should they be needed.
To perform the repair install, go Start - Computer - insert the install disk and double click on the drive which should start the process - you may have a small amount of user input such as agreeing to the EULA but once it starts, it will just get on with it.
You'll then be looking at the Windows Updates wanting to download and install or you may have to do a manual check for updates, but I'd change the update settings to Let me choose... and then you can vet them before they download.
One update I think you look for is KB2952664 - this is a Telemetry update which sends data back to MS and is a spy, but it's up to you.
I know a few including myself that hide this update when it is offered.
FreeCat:
Thanks, Boggin, for your help. OK Backerupper has been running for about 10 hours and is at about the 25% mark. That error happened within a hour last time, so I think we are clear of that. the reboot and reinstall did it.
I will wait and watch and keep you informed of my next steps.
BTW, how is windows create image called. I never knew there was one.
Thanks again for your help.
Boggin:
It's all I use, but go Start - Control Panel - System and Security/Back up your computer and you will see the option in the left pane where you can also create a System Repair disk.
Before you go for the repair install, see if an offboot sfc /scannow will repair that file.
You may need to change the boot order to boot up with the install disk so tap F12 as you switch on, use the cursor keys to select the DVD drive, insert the disk and press enter.
You may be presented with an inverse window with Windows Setup [EMS Enabled] highlighted - just press enter.
Use the dropdowns to change/confirm Language and Time and Currency format - Next - then on the Install screen click on Repair your computer bottom left then select Command Prompt.
At the prompt enter bcdedit |find "osdevice"
You need to enter this cmd as Windows doesn't always see the volume as being in C:
That is a Pipe symbol before find and is the uppercase of \ then use the partition letter that gives you instead of the X I have used and enter this cmd -
sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows
Note there is a space before each /
You won't see the % progress as you would when running a normal sfc /scannow but it will report the same as a normal one would on completion.
If that says it can't repair all files as well then you will need to perform the repair install.
If it says it has repaired files then enter exit in either case to close the cmd window, remove the install disk and restart and then run another sfc /scannow to see what it reports.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version