Location:
State:
Carrier
Country
Status

bad system config info


I used avg tuneup to check the disk for errors on next boot and my computer turned off while it was checking for errors.
After this happened I can't get windows 10 to boot into login. I get a message saying it can't boot windows and I get a bad system config info error.

I am using a N5050 Inspiron Dell Laptop.
I tried booting into command prompt and running the command chkdsk /f /r /x and when it finishes it says it didn't fix anything or fine any errors. Ubuntu says it has bad sectors when I tried to run a fix on the partition in gparted.

I tried burning easyre windows 10 recovery disc on usb and DVD-r without any luck on ubuntu. Yes I know how to setup my computer to boot from cd/dvd or usb. I only have access to windows command prompt and ubuntu system on external usb jump drive I have no access to windows computer.

Hi ian4,

Welcome to the 10blog.

Likely, some system files are damaged.
We need to be careful with this as the system will, after too many attempts to boot, lock the drive to prevent damage.
Please try following:
  • Open an admin command prompt
  • Copy/paste "sfc/scannow" (without quotes) and press enter
  • When it finished reboot your system
  • Open again an admin command prompt
  • Enter sfc/scannow again

If sfc/scannow does NOTsay"Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}WindowsLogsCBS, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

I run the command sfc/scannow and says I need to reboot like you said.
However my computer boots differently each time. First it boots up with normal windows booting screen then screen comes up and says windows encounter an error and needs to reboot bad system config info error. Then when I reboot it runs windows repair and diagnosing then after they are finished nothing is fixed and gives me options to fix the problem my self with command prompt and such. I tried resetting the windows without removing my personal files and it fails and says it has done nothing to the machine.
Each time I reboot I get the repair and diagnosing screen then self repair options at the end and then when I boot again it says it encountered an error and needs to reboot it does this in this order each time I reboot. So when I boot after running the sfc/scannow command in the admin command prompt and reboot how do I get a command prompt if it says it encountered an error and needs to reboot??

Please try following
Run the following commands at the command prompt.

diskpart
list volumeNOTE:Note the volume letter where the Windows OS is installed.
exit

bcdboot X:windowsNOTE:Replace "X" with the volume letter of the Windows OS partition.

For example, bcdboot c:windowsor bcdboot d:windows(see screenshots below).

If the drive letter is incorrect, you will receive the following error message: "Failure when attempting to copy boot files."




Credits: @genet or genet

after I do what you say. I boot up after it completes and then I get this instead.

It says that it has been booted multiple times and says you need to use a recovery disc now or usb if you don't have one contact your device manufacture.
gives this error code 0xc0000001

Then says press enter to retry then below that it says press f8 to select boot options.

I am wondering, do you know what AVG wanted to modify?

I have no idea. I think it just did a normal chkdsk for errors and if found fix them. The chkdsk screen after reboot looked the same as before when I did it without using avg tuneup.

Ok,

I don't know what has been damaged, but I think we need to try this step by step.
First the boot files, in command prompt enter the following command
Code:
bootrec /rebuildbcd

What should I do now to get into a command prompt again when it boots?

Do I press f8 and select one of the options?

bad system config info