using the SysRescue cd problems

[kkay 0]

I got the SysRescue cd/dvd earlier.  I did not try it out until now.  I had to change the bios settings to allow the internal ODD device to be first on the boot list.  Still it did not boot off the cd, but it sounded like it was reading it.  I could change boot to Legacy, but it asked me if I was sure I wanted to do that.  I decided I was a little fearful of that, and didn't do it.  I was going to change it back to UEFI after it rebooted from Windows.  I found this, but only the first page will print for some reason. 

 

hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3135&locale=en_US

 

It says nothing about this.  Any suggestions?

[Arakasi 549]

Hi kkay

Did you create your own SysRescue or had a copy sent ?

Do you have another computer to try and test the boot loader ?

[kkay 0]

Hi Arakasi.  I made the copy myself.  I did not have a copy sent, I didn't even know you could do that.  I do not have another computer to try the SysRescue cd on.  I have a laptop, but the jack is not working on it, so I can't even plug it in. 

[Arakasi 549]

Do you have any other cd's that are bootable, so we may ascertain whether its the cd or the pc?

A great supplement would be the windows disc.

If it boots, we may need a second look at the compilation of the SysRescue.

[kkay 0]

Arakasi, I tested my Macrium Reflect boot cd, it works.  I am on a trial of the Macrium Reflect standard software.  I did have to go in bios and change the setting to allow boot from cd/dvd first.  After that it worked.  (I had to use the ISO copy to burn though, it would not burn the WinPE for some odd reason)

[Arakasi 549]

Great so your all good now ?

If not, i would try making the CD again.

[kkay 0]

No, it is not good.  The SysRescue does not boot.  I don't know if I am keeping Macrium Reflect, and I don't think it works, unless you have that program.  I am on a trial of it.  Besides, I want the SysRescue to work, so I can get it to help in case of catastrophic infection.  I guess I will try making the cd again.  Thank you for trying to help me.

[Arakasi 549]

If the cd does not boot, you will certainly need to try creating it again.

Make sure your following closely the directions here :
 

How do I use ESET SysRescue to create a bootable USB disk, CD or DVD on a 32-bit Windows system?

[kkay 0]

Thank you.  I have the 64 bit OS though.  hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2965

 

 

I did these steps.<<<

 

1. Download the Microsoft Windows Assessment and Deployment Kit (ADK).
   1. Click Save File when prompted and save the file to your Desktop. While the initial ADK.exe file is a small download, the installer will download additional material that requires 1.7GB of hard drive space.
       
2. Once the download completes, double-click the .exe file you just downloaded to install ADK.
    
3. After installing ADK, restart your computer.
    
4. Proceed to the Create a SysRescue CD, DVD or USB disk section.>>>

I have Win8.1 64 bit.  I have the ADK.  The directions were a little fuzzy for me.  It has been a little while since I did this disk.  I had trouble several times in the past getting that cd to burn.  I used the ESET Nod32, TOOLS, then SysRescue to do the cd/dvd with.  Now I forget which it was that I used, but I think it was a dvd.

[kkay 0]

Okay, I just burned another disk.  It did not give me any trouble at all.  It said it was creating a PE.  I think this is why it isn't working.  The Macrium Reflect would not burn a proper PE file either.  I had to use an ISO file to boot from instead.  (via the Macrium Reflect software)  This must have something to do with going from Win8 to Win8.1.  (The update to 8.1 was from the store)  I asked the Macrium Reflect tech, and he said just use an ISO file, to get the boot cd.  I had asked him if downloading a PE5 file would work, but he just suggested the ISO file.  So now I have two SysRescue disks, and neither boot.

[Arakasi 549]

I know you have 64bit, but did you use a 32bit msi file to create the image ?

[kkay 0]

Arakasi, I do not remember.  I do remember when I first tried to get this boot cd done, after the ADK file, it was looking for a msi file.  (the SysRescue program was looking)  I do not know anything about msi files.  How can I check that?  If I knew the exact name, that would make it easier. 

[kkay 0]

I think I might be better off just making a PE5, and trying another image.  (If I could follow instructions on that) 

[Arakasi 549]

hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2885

 

VIsit above link and download version 4 or 5 , but DL 32bit version.

During the SysRescue Wizard, it asks you to select MSI.

Use the one you downloaded instead of whatever automated process it uses.

Revisit the origional link for instructions as it will guide you on the manual MSI import.

[kkay 0]

Arakasi, I appreciate the tip there.  It seems that my File History backup was not right either.  I did a SFC /scannow and it had corrupted files in Windows.  I am really getting frustrated.  I have a copy of the CBS log, but can't make heads or tails of it.  I may have to just go to the manufacturer disk, and start from scratch.  I feel this whole issue is from the Win8.1 update.  I had Win8 on this computer, and made the sad mistake of updating from the store, which Windows directed me to do.  I have spent untold hours trying to sort out the mess ever since.  Now I am not sure if any of my backups are worth a flip.  At least I have my pics, and documents saved to a flash drive.  I looked at the CBS log, but I don't know what to look for in it.  Let's just say I'm not a happy camper right at the moment. 

Edited January 24, 2014 by kkay

[Arakasi 549]

I am familier with sfc .

You can PM me your log.

Or follow this link if you would like to research : hxxp://support.microsoft.com/kb/928228

 

However i would run sfc multiple times if you have errors. 3 or 4.

[kkay 0]

I ran it 3 times.  I tried doing the stuff in the link you sent.  I had already found it, but it wasn't working for me, or I was doing something wrong.  I could send you the last log.  I think it is way too large for you to get in a pm though.  It is almost 5000KB long.  I couldn't get the part where you find out just what the issue was, the corrupted files.  I was in command prompt, administrator mode too. The commands to find out did not work in command prompt for some odd reason.  I wish Microsoft had a program to find the corrupted file, via an online scan if nothing else, then give you an update, or allow you to get the good file that is needed.  I have spent hours on this today, and I'm not better off than I was yesterday.  I give up for this evening.  It is after midnight now.  Thank you Arakasi for trying to help me.  I sure appreciate it.

[Arakasi 549]

No problem.

Have you thought about creating a usb SysRescue instead ?

 

Regarding the huge cbs log. It is probably compiled of every thing. You could copy the log, save it elsewhere too, delete the original, and run sfc again thus creating a new, smaller log.

However in my experiences, when sfc can no longer repair the issues found, a repair on windows installation is needed with the windows disc, or reinstall.

[kkay 0]

I have not really thought about it. If my windows files are corrupted, I think the problem will still exist with a usb flash drive.  I have no idea on where to begin with a repair on windows installation.  I haven't had to do anything like that since Win95 or so...lol.  This might not work even if I do.  The files may have become corrupted going from Win8 to Win8.1 in the store.  Before that my computer ran great.  Then I was forced into the update via the store, which ticked me off.  I could not get out of it.  I had lots of problems when I restarted after that update.  I finally got the Dell tech to help me, since I was still under warranty then.  Even she spent hours and hours trying to get my computer back to normal status. Mainly there were driver problems.  It shut off my firewall, and wouldn't let Comodo run, it did not automatically make C drive ready to set restore point.  (it never gave warning that it wasn't there)  Just loads and loads of stuff like that.

    After that I was able to burn a Win8.1 disk.  You only get one shot at it.  If it didn't burn well, I am in a mess.  I liked it better when you got a Windows disk, and could use it however many times you needed.  They already know your copy is genuine because the number is embedded in the motherboard, or something like that.  Not everyone is a computer geek, and Microsoft should know that by now.  They should come up with a computer operating system that can fix abnormalities like this, without the user jumping through countless hoops.  Maybe some like the hoops.  I just want my pc to run the way it should, do backups, and USE the computer without constant issues.  I have always had Windows, from the start.  But lately I am wondering if I should try Linux in the future. 

[kkay 0]

Well I finally got the corrupted file issue worked out.  Now I am going to try to manually install that 32 bit download, and get the msi file from that.

[Arakasi 549]

Kkay,

 

Great news, good luck and let us know how it goes.

[kkay 0]

Arakasi, I just tried it out, and I don't think it did right, again.  I downloaded the 32 bit installer.  It is in my download folder.  I put change in the SysRescue part where you could select .msi file.  I clicked browse, then found that file, in the download folder.  Then I just clicked on next.  (I had selected the msi bullet) I did not click on update folder.  I left the bullet preselected at the ESS /EAV folder. Then I created it.  I clicked F12.  It said boot mode set to UEFI Secure Boot ON.  Next it said UEFI Boot ...and it did not give another choice.  I had set the bios to take the ODD first, and the UEFI second in sequence.  I hit enter on windows boot manager, there was not another choice to select.  It rebooted.  Since I did not see another option come up, I take that as it did not work.  I know the Macrium Reflect boot disk works.  It allowed 2 choices, and I hit enter on that one.  Please tell me what I am doing wrong.