51 replies to this topic

[pq10]

Hi,

 

I know this topic has been posted a year ago, but still hope to get some suggestions from you guys, because I have the exactly same problem here, and I am lost in the "booting steps".

 

The urgent question I really need an answer is: if I install windows 7 via the removable usb drive, does it affect the original operating system installed in my internal hard disk? (I know this seems like a stupid question, but I really not good in computer or IT).

 

Thank you in advance

[Wonko the Sane]

WHICH problem?

WHICH booting steps?

 

Please detail EXACTLY YOUR situation (DO NOT assume that anyone's else is the same as YOURS).

 

Standard Litany, please:

http://homepage.ntlw...ard-litany.html

 

Of course if you re-install (no matter if from "removable" drive, DVD, Network or *whatever*) you are going to OVERWRITE parts of the already installed OS, that will be SEVERELY affected (in the sense that it will be not as it was before, you will need to reinstall all your programs).

 

Wonko

[pq10]

 

WHICH problem?

WHICH booting steps?

 

Please detail EXACTLY YOUR situation (DO NOT assume that anyone's else is the same as YOURS).

 

Standard Litany, please:

http://homepage.ntlw...ard-litany.html

 

Of course if you re-install (no matter if from "removable" drive, DVD, Network or *whatever*) you are going to OVERWRITE parts of the already installed OS, that will be SEVERELY affected (in the sense that it will be not as it was before, you will need to reinstall all your programs).

 

Wonko

 

Apology for not following the Standard Litany, and thank you so much for replying my question.

 

I am using windows 7 pro (64bit, no Install DVD or Repair Disc), and after tried to run the software Spyhunter to fix the "kidnapped" chrome (the Spyhunter is said able to fix that problem, so here I am now), my laptop only goes to a black screen with the message "Error 13: Invalid or unsupported executable format" after restart. If I press any key to continue, it enters a red screen with a menu list, but, whichever option I have selected, it only brings me back to the black scree (black screen, press any key to continue -> red screen, select an option and press Enter -> back to the original black screen).

 

Then, I found this post and your suggested solution.

 

I tried this:

 

When you are in the last screen (at the grub> prompt) type:

find /bootmgr

[ENTER]

It should most probably give you (hd0,0) as result.

Type:

find --set-root /bootmgr

[ENTER]

and then:

chainloader /bootmgr

[ENTER]

boot

[ENTER]

 

What happens?

 

Wonko

after find /bootmgr, it didn't show any result.

 

 

Then, I follow this:

 

Ideally you should make the device bootable.

A suitable tool is RMPREPUSB:

http://www.rmprepusb.com/

if you additionally add to it the Easy2boot:

http://www.rmprepusb...-maintain/e2bv1

it will be easier later to copy to it (and have it boot) the downloaded Windows 7 .iso.

 

To hopefully clear the current situation of your PC:

1. the Spyhunter installed to it a version of grub or grub4dos
2. the "remedy" in case of issues is to boot from a Windows 7 install DVD and run the bootsect.exe tool to restore the original bootsector of the active partition/volume

Normally grub4dos can directly chainload the BOOTMGR file (i.e. do the same thing that a Windows 7 bootsector does), when this succeeds, the Windows 7 on the internal disk boots fine, and then form it you can run the bootsectexe (and/or use some other tools/ways to better diagnose the issue and fix it).

In your case attempting doing that resulted in an error, what we don't know if the particular version of grub/grub4dos has this function not working or disabled, or if the BOOTMGR has been changed/corrupted by the Spyhunter, or if the issue is because your system is 64 bit (I doubt it, but cannot really say for sure), or if something else is happening.

 

The intended procedure is the following:

1. boot from an external USB device partitioned/formatted by RMPREPUSB, which includes a version of grub4dos surely working in chainloading the BOOTMGR
2. if that fails, add to the USB device the WIndows 7 .iso, boot to it and then be able to both restore a "surely clean" BOOTMGR and replace the bootsector using bootsect.exe.

 

Wonko

 

Here what I did:

1. I prepared a 64GB (3.0) USB stick as my bootable device. I followed the steps in following page, but at step 5 "Install grub4dos button", the pop up window message is only for MBR (not PBR), I clicked yes, then another window pop up asking whether I want to overwrite it, I clicked Cancel (because I am not sure whether it should be overwritten). http://www.easy2boot...sing-rmprepusb/"

 

2. After the removable USB device is prepared (or it is not completely prepared?), I followed the instructions ( of Option 1) in another page to put the iSO into the device. 

http://www.easy2boot...-payload-files/

 

After these two procedures, I plugged the USD device to my laptop, then made the USD device the primary disc in BIOS boot options. The Easy2Boot interface did show up, but among the options in the menu list, I didn't see any win 7 but only Grub4docs. 

 

And the result of course is fail, then I dug into the rmprepusb and easy2boot website again.

 

In second try, these are what I did:

1. Same as above

 

2. Same as above

 

3. Convert the win 7 pro 64bit ISO file to .imgPTN, put it in the \_ISO\MAINMENU folder, then run WinContig in RMPREPUSB.

 

4. Plug the device again to the laptop, in E2B menu list, an option "Install Win 7 64bit" appeared. I clicked on that option, there were few steps in between, but the last step I remembered was, I selected "BOOT from this device (MBR mode)". 

 

I finally left the black/red screen, and enter win 7 screen. After selected language, it gives me two options, "Install now" and "Repair your computer". This is where my first posted question come from. 

 

The result I am hoping to get is, able to boot normally again from the internal hard disk of my laptop (works as before the Spyhunter problem occurred), and all the data in the hard disk is not lost. Would this be possible? 

[Wonko the Sane]

The "red " screen is most probably a grub4dos menu.lst.

From it if you press the "c" key, you should land to a "grub>" prompt.

In this typing the command 

find /bootmgr

[ENTER]

should work and give as output a drive (like (hd0,0), (hd0,1) etc.).

 

Anyway, when you boot from the USB stick to the Windows 7 install .iso, when you are asked to choose langauage, try pressing SHIFT+F10, a command prompt window should appear.

 

From it you should be able to do what is needed, point being is that before doing it we need to understand WHAT is needed.

 

There are several different ways, particularly on a laptop or however big OEM PC, in which the Windows 7 could have been installed, and the procedure to fix the booting is different depending on the actual setup.

The traditional way to install a NT OS was to have the same volume (usually given the drive letter C:\ ) be at the same time "boot" and "system", Windows 7 has introduced a new installation method where there is a smallish partition (that MS call "System", but that is actually the "Boot" one) that contains the BOOTMGR and the \boot\BCD, i.e. the two base files needed to boot your system.

 

From previous reports, that stupid Spyhunter crap exists in different versions and they might behave differently (possibly depending on how the original system was setup) so we need to understand what changes it has done to your system.

 

Can you get to that SHIFT+F10 command prompt?

 

The idea is to first understand, by running a few commands, in which situation is your system and then attempt to fix it, in theory if you go on and choose the "Repair your computer" everything should be automated, but in practice there is the risk that *something* is not as the tool expects and the result of running it might not be the expected one.

 

But it would probably be easier/faster if you can actually get to the grub> prompt and run from it a few commands, check this thread:

http://reboot.pro/to...ptop-wont-boot/

basically even if the BOOTMGR has been overwritten/deleted/renamed, there should be a copy of it available on the original Windows 7 install, which - if the other conditions are OK - we can use to boot to the Windows 7.

 

Wonko

[pq10]

The "red " screen is most probably a grub4dos menu.lst.

From it if you press the "c" key, you should land to a "grub>" prompt.

In this typing the command 

find /bootmgr

[ENTER]

should work and give as output a drive (like (hd0,0), (hd0,1) etc.).

 

Anyway, when you boot from the USB stick to the Windows 7 install .iso, when you are asked to choose langauage, try pressing SHIFT+F10, a command prompt window should appear.

 

From it you should be able to do what is needed, point being is that before doing it we need to understand WHAT is needed.

 

There are several different ways, particularly on a laptop or however big OEM PC, in which the Windows 7 could have been installed, and the procedure to fix the booting is different depending on the actual setup.

The traditional way to install a NT OS was to have the same volume (usually given the drive letter C:\ ) be at the same time "boot" and "system", Windows 7 has introduced a new installation method where there is a smallish partition (that MS call "System", but that is actually the "Boot" one) that contains the BOOTMGR and the \boot\BCD, i.e. the two base files needed to boot your system.

 

From previous reports, that stupid Spyhunter crap exists in different versions and they might behave differently (possibly depending on how the original system was setup) so we need to understand what changes it has done to your system.

 

Can you get to that SHIFT+F10 command prompt?

 

The idea is to first understand, by running a few commands, in which situation is your system and then attempt to fix it, in theory if you go on and choose the "Repair your computer" everything should be automated, but in practice there is the risk that *something* is not as the tool expects and the result of running it might not be the expected one.

 

But it would probably be easier/faster if you can actually get to the grub> prompt and run from it a few commands, check this thread:

http://reboot.pro/to...ptop-wont-boot/

basically even if the BOOTMGR has been overwritten/deleted/renamed, there should be a copy of it available on the original Windows 7 install, which - if the other conditions are OK - we can use to boot to the Windows 7.

 

Wonko

Yes, I can get to the SHIFT+F10 command prompt. 

And, as your suggested to get to the gub>prompt, do you mean the Grub Command Line in following picture?

https://www.dropbox..../image.jpg?dl=0

(this is the red screen shown up after I pressed any key to continue in the black screen with the message "Error 13: Invalid or unsupported executable format")

 

 

Ps: the notebook having problem is hp pavilion g4, and sorry, I don remember the specs...

Edited by pq10, 01 March 2015 - 02:50 PM.

[Wonko the Sane]

Yes, I can get to the SHIFT+F10 command prompt. 

And, as your suggested to get to the gub>prompt, do you mean the Grub Command Line in following picture?

https://www.dropbox..../image.jpg?dl=0

(this is the red screen shown up after I pressed any key to continue in the black screen with the message "Error 13: Invalid or unsupported executable format")

Yep.

That is an obsolete and never "recommended" version of grub4dos 0.4.4 2009-09-03 (the only 0.4.4 version usable is latest 2009-16-10 just for the record).

 

Though the posted screenshot seems more like a (WAREZ) SLIC Loader screen than a Spyhunter one

 

Anyway when you are at that screen, if you press the "c" key or you choose last line in the menu "Grub Command Line" and press [ENTER] you should land to a:

grub>

command line prompt.

In it you should be able to run (grub4dos) commands.

More or less we need to understand how many partitions are on that disk, which type they are, etc.

Run the commands detailed here:

http://reboot.pro/to...oting/?p=179624

and report.

 

Any info you remember about how the disk is partitioned, which drive letters were in use, etc. would as well be useful.

 

Wonko 

[pq10]

ok, here is the report .... and I have only 2 partitions (C for windows and programs & D for others)

 

https://www.dropbox..../image.jpg?dl=0

Edited by pq10, 01 March 2015 - 03:42 PM.

[Wonko the Sane]

Good, so you have a "plain enough" install, seemingly without the 0x27 "System" partition.

 

Try this set of commands:

http://reboot.pro/to...-boot/?p=189650

 

Wonko

[pq10]

"plain enough" install means need more repairs?? 

 

ok, next results...

 

https://www.dropbox..../image.jpg?dl=0

[Wonko the Sane]

"plain enough" install means need more repairs?? 

 

ok, next results...

 

https://www.dropbox..../image.jpg?dl=0

Naaah, it means that repairing it should be easier/simpler .

 

There are three "suspect" files in that ls output:

1. sh4ldr (likely a grldr renamed)
2. bootmgr (likely - since grub4dos cannot chainload it some modified file)
3. bootmgr_ (which could be the original BOOTMGR renamed )

 

 

But I wanted the results of these commands:

http://reboot.pro/to...-boot/?p=189650

i.e.:

 

root (hd0,0)
ls /Windows/Boot/PCAT/bootmgr
chainloader /Windows/Boot/PCAT/bootmgr
boot

 

 

Wonko

[pq10]

Naaah, it means that repairing it should be easier/simpler .

 

There are three "suspect" files in that ls output:

1. sh4ldr (likely a grldr renamed)
2. bootmgr (likely - since grub4dos cannot chainload it some modified file)
3. bootmgr_ (which could be the original BOOTMGR renamed )

 

 

But I wanted the results of these commands:

http://reboot.pro/to...-boot/?p=189650

i.e.:

 

 

Wonko

 

ok.......so the RESULT is, the notebook enters its win 7 pro home screen, and everything is back without missing!       

Million thanks to your patience and helpful instructions 

 

And, my last question is, do I have to do something else to my notebook to make sure the same problem won't occur again (or what action should I take to prevent the same problem)?

[Wonko the Sane]

ok.......so the RESULT is, the notebook enters its win 7 pro home screen, and everything is back without missing!       
Million thanks to your patience and helpful instructions 

Very good.
 

And, my last question is, do I have to do something else to my notebook to make sure the same problem won't occur again (or what action should I take to prevent the same problem)?

Well, right now we "worked around" the issue, now it's time to understand what is the current "automatic" boot sequence and correct it so that at each reboot you don't have to go this procedure.

Most probably - but cannot say for sure - the boot sequence has been altered by replacing the original BOOTMGR in your C:\ with *something* else (but it is also possible that the bootsector has been changed to load another file).

Ideally you should (better be safe than sorry):
1) create on your C:\ drive a file named BOOT.INI with these contents (you should be able to use Notepad to copy and paste the following, make sure to save as BOOT.INI and NOT as -say - BOOT.INI.TXT):

[boot loader]
Timeout=15
default=C:\grldr
[operating systems]
C:\grldr="grub4dos"
C:\sh4ldr="Some Spyhunter crap"

2) get a recent version of grub4dos, download this:

http://dl.grub4dos.c...c-2015-02-09.7z

open it with 7-zip and extract from it only the grldr file, copying it to your C:\

3) Rename the C:\BOOTMGR_ (note the underscore) to (say) OLDBOOTMGR_

4) Copy the BOOTMGR file from C:\Windows\Boot\PCAT\bootmgr to C:\bootmgr, overwriting the one that is currently there.

 

You might need to set explorer to show hidden and sytem files or similar.

 

Then try rebooting.

 

If the matter was just a modified BOOTMGR, the PC should boot normally, and you should have a choice between Windows 7, grub4dos and "Some Spyhunter crap".

 

Choose the Windows 7 and if it boots normally everything is fine and you can delete the OLDBOOTMGR_, the sh4ldr, the grldr and the boot.ini.

 

If this doesn't happen, report what happens.

 

Wonko

[pq10]

It does boot normally, but couldn't delete the OLDBOOTMGR_ (pop up window says I need permission from TrustedInstaller to make changes to this file).

 

And, the sh4ldr folder was in C drive, but "disappear" automatically after I uninstall the spyhunter software.   

 

Then I found spyhunter.fix file in C drive, can I delete this as well??

[Wonko the Sane]

Yes, you can delete the spyhunter.fix file fine.

 

To delete the OLDBOOTMGR_ file it is possible that you can get the needed privileges by taking ownership of the file, see:

http://helpdeskgeek....ustedinstaller/

 

Or you could to using the boot DVD/USB stick and see if in the PE command line (Shift+F10 as seen before) you can delete it.

 

There are a couple ways to get TrustedInstaller privileges, i.e. to "impersonate" TrustedInstaller, see here:

http://www.msfn.org/...ustedinstaller/

http://developex.com.../devx-exec.html

http://reboot.pro/fi...d-runfromtoken/

but it should not be needed, first method above should work fine.

 

Wonko

[cdob]

do I have to do something else to my notebook to make sure the same problem won't occur again (or what action should I take to prevent the same problem)?

Yes, the issue relates to Spy Hunter.
http://www.techsuppo...ate-494257.html

Asks the manufacturer to fix this in future.

[pq10]

To Wonko,

 

Yes, the first method works fine 

 

All instructions completed, problem solved, and case closed 

 

To cdob,

 

Ok, thank you for your suggestion too 

 

Thank you so much for all the supports ! 

[Wonko the Sane]

To Wonko,
 
Yes, the first method works fine 
 
All instructions completed, problem solved, and case closed 

 
Good.  
 
 

Asks the manufacturer to fix this in future.

To cdob,
 
Ok, thank you for your suggestion too 

 
You may want to write personally to Alec Malaspina, he is the Vice President and he reads personally the complaints e-mail box :
http://www.scambook....32868/SpyHunter
http://www.complaint...er-c262520.html
 

I am the Vice President of Technical Support and Research at Enigma Software Group. I read the post above and I would like to let you know that we have an email specifically for complaints. You or anyone can submit a complaint and I can assure you that we will find a suitable solution for any problem that is related to SpyHunter or to our service.

If you have any questions or complaints, please send us an email to complaints@enigmasoftware.com. I personally read all emails from that account.

At Enigma Software Group, we work hard to maintain the best level of service and make sure that every customer becomes a satisfied customer.

Regards,

Alec Malaspina
Enigma Software Group USA, LLC.

Wonko

[sseth]

Hello,
I have the same problem with Spyhunter and Grub4dos, when i boot my pc, i go into grub4dos 0.4.3 window with 3 options: Spuhunter, Windows XP and Windows Vista/7. After 3 sec. it automatically boot Spyhunter, after few sec pc restarts and again boot Spyhunter... but when i chose Windows Vista/7 pc boot as it should be, without any problems. How do i get rid of that spyhunter and make my pc boot normally again? because now i have to click any button to stop that automatic boot... I have typed few commands in grub command line and this is what i got:

grub> geometry (hd0)
drive 0x80(LBA): C/H/S=60802/255/63, Sector Count/Size=976784130/512
Partition num: 0, Filesystem type is ntfs, partition type 0x11
Partition num: 1, Filesystem type is ntfs, partition type 0x7
Partition num: 2, Filesystem type is ntfs, partition type 0x7
grub> root (hd0,0)
Filesystem type is ntfs, partition type 0x11
grub> cat /b
Possible files are: Boot bootmgr bootmgr_ BOOTSECT.BAK
grub> cat /boot/
Possible files are: BCD BCD.LOG BCD.LOG1 BCD.LOG2 BCD~1.LOG BCD~2.LOG BOOTSTAT
.DAT cs-CZ da-DK de-DE el-GR en-US es-KS fi-FI Fonts fr-FR hu-HU it-IT ja-JP ko
-KR memtest.exe nb-NO nl-NL pl-PL pt-BR pt-PT ru-RU sv-SE tr-TR zh-CN zh-MK zh-
TW

Edited by sseth, 09 May 2015 - 07:13 PM.

[cdob]

How do i get rid of that spyhunter and make my pc boot normally again?

Do you like to get spyhunter menu in future? Do you like to to change default boot selection?
Then edit menu.lst default section.

Do you like to remove sphyhuter?
http://reboot.pro/to...en/#entry181323

[Wonko the Sane]

It seems like bootsect /nt60 SYS /MBR (which just for the record re-writes the MBR Code with the original Windows Vista/7/8 code, chainloading the bootsector of the active partition and re-writes the partition/volume bootsector using some code that chainloads BOOTMGR) is not "enough" in all cases.

 

Some versions might rename/change the actual BOOTMGR file, so it is advised to additionally restore the BOOTMGR copy that can hopefully be found in C:\Windows\Boot\PCAT\bootmgr to root of the partition, see also:

http://reboot.pro/to...-boot/?p=189650

http://reboot.pro/to...creen/?p=191071

and following.

 

Wonko

[darush2002001]

i had same problem...

 

it was so easy

just place the win7 CD in drive and put the 1st boot on CD.

then start installing it.

but in installing go to repair the windows and then startup repair.... then your pc will be restart and all thing is OK.

good luck

[Wonko the Sane]

i had same problem...
 
it was so easy
just place the win7 CD in drive and put the 1st boot on CD.
then start installing it.
but in installing go to repair the windows and then startup repair.... then your pc will be restart and all thing is OK.
good luck

 

Really?

We never thought of that , maybe because :

 

 

I am using windows 7 pro (64bit, no Install DVD or Repair Disc), ...

 

 

Wonko

[Navin01]

Very good.
 

Well, right now we "worked around" the issue, now it's time to understand what is the current "automatic" boot sequence and correct it so that at each reboot you don't have to go this procedure.

Most probably - but cannot say for sure - the boot sequence has been altered by replacing the original BOOTMGR in your C:\ with *something* else (but it is also possible that the bootsector has been changed to load another file).

Ideally you should (better be safe than sorry):
1) create on your C:\ drive a file named BOOT.INI with these contents (you should be able to use Notepad to copy and paste the following, make sure to save as BOOT.INI and NOT as -say - BOOT.INI.TXT):

[boot loader]
Timeout=15
default=C:\grldr
[operating systems]
C:\grldr="grub4dos"
C:\sh4ldr="Some Spyhunter crap"

2) get a recent version of grub4dos, download this:

http://dl.grub4dos.c...c-2015-02-09.7z

open it with 7-zip and extract from it only the grldr file, copying it to your C:\

3) Rename the C:\BOOTMGR_ (note the underscore) to (say) OLDBOOTMGR_

4) Copy the BOOTMGR file from C:\Windows\Boot\PCAT\bootmgr to C:\bootmgr, overwriting the one that is currently there.

 

You might need to set explorer to show hidden and sytem files or similar.

 

Then try rebooting.

 

If the matter was just a modified BOOTMGR, the PC should boot normally, and you should have a choice between Windows 7, grub4dos and "Some Spyhunter crap".

 

Choose the Windows 7 and if it boots normally everything is fine and you can delete the OLDBOOTMGR_, the sh4ldr, the grldr and the boot.ini.

 

If this doesn't happen, report what happens.

 

Wonko

Hey,

I followed the "bookmgr_" trick to boot normally into Windows 7.

 

and followed all the steps as specified above to get rid of "spyhunter" but could not find the file "C:\BOOTMGR_"

 

will someone please tell me how to follow step #3

 

"3) Rename the C:\BOOTMGR_ (note the underscore) to (say) OLDBOOTMGR_"

 

Thanks in advance

Edited by Navin01, 03 March 2017 - 04:26 PM.

[Wonko the Sane]

Hey,

I followed the "bookmgr_" trick to boot normally into Windows 7.

 

and followed all the steps as specified above to get rid of "spyhunter" but could not find the file "C:\BOOTMGR_"

 

will someone please tell me how to follow step #3

 

"3) Rename the C:\BOOTMGR_ (note the underscore) to (say) OLDBOOTMGR_"

 

Thanks in advance

Maybe in your case there is no need of doing step 3.

There were reports that the "real", "original" BOOTMGR was replaced by another loader and renamed as BOOTMGR_, then there were some reports that the (renamed) BOOTMGR_ was anyway modified and it was not bootable from grub4dos and thus the safest is to copy to root the copy that is normally in C:\Windows\Boot\PCAT\bootmgr, it seems like the presence of this BOOTMGR_ file (that was in the pq10's ls output in grub4dos ):
http://reboot.pro/to...e-2#entry191062

is not in all installs (it likely it depends on specific versions of spyhunter or on specific *whatever* system setups), maybe it is not in yours, or maybe it is hidden/system, see also:

...
 
Most probably the C:\bootmgr_ is a Hidden and System file, you will need to set Explorer to show such files, *like*:
http://www.howtogeek...-windows-vista/
in order to "see" it and, after the computer boots successfully after the repair, delete it.
...

Anyway, it is just a "cleaning" step, if you have a file that won't be used anymore it makes sense to delete it, but leaving it will only clutter - maybe - the output of ls or DIR, anyway I will take back:

 

3) Rename the C:\BOOTMGR_ (note the underscore) to (say) OLDBOOTMGR_

and rephrase it as :

 

3) IF a file C:\BOOTMGR_ (note the underscore) exists, then rename it to (say) OLDBOOTMGR_

 

The actual "latest" [Solution] is here (just in case):
http://reboot.pro/to...s-7-unbootable/

 

 

Wonko

[Navin01]

Maybe in your case there is no need of doing step 3.

There were reports that the "real", "original" BOOTMGR was replaced by another loader and renamed as BOOTMGR_, then there were some reports that the (renamed) BOOTMGR_ was anyway modified and it was not bootable from grub4dos and thus the safest is to copy to root the copy that is normally in C:\Windows\Boot\PCAT\bootmgr, it seems like the presence of this BOOTMGR_ file (that was in the pq10's ls output in grub4dos ):
http://reboot.pro/to...e-2#entry191062

is not in all installs (it likely it depends on specific versions of spyhunter or on specific *whatever* system setups), maybe it is not in yours, or maybe it is hidden/system, see also:

 

 

Anyway, it is just a "cleaning" step, if you have a file that won't be used anymore it makes sense to delete it, but leaving it will only clutter - maybe - the output of ls or DIR, anyway I will take back:

and rephrase it as :

 

The actual "latest" [Solution] is here (just in case):
http://reboot.pro/to...s-7-unbootable/

 

 

Wonko

Thanks a ton , Wonko.

 

Though the problem is after the reboot....I have been facing the same problem and had to enter the commands every time I tried to start the PC. even after following the steps in this thread.

 

trying the below mentioned thread now.

 

regards.