Author Topic: Recently installed Windows Repair v3.7.0, spotted 'glitch' after Repairs phase  (Read 3120 times)

0 Members and 1 Guest are viewing this topic.

Offline doomkrad

  • Newbie
  • *
  • Join Date: Feb 2014
  • Posts: 5
  • Karma: 0
    • View Profile
Today I was informed my Windows Repair installation needed an update, so I did a fresh install (couldn't find a way of applying the update instead). I am now on Version 3.7.0.
I also performed a repair and noticed that although:
a. the use of Safe Mode with Networking is advised and
b. a Reboot To Safe Mode button is provided in each tab
after the Repairs rebooting directly from the Command Prompt window leads to a restart in Normal Mode, NOT to Safe Mode! So I had to (once more) 'manually' reboot to Safe Mode, in order to perform the second Repairs iteration.
So it looks like a tweak of the Repairs phase/step is needed.
Many thanks in advance.

[ Windows 7 Ultimate x64 SP1 ]

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9786
  • Location: UK
  • Karma: 120
    • View Profile
I have the Pro version which has an auto update option and 3.7.0 booted up fine into Safe Mode with Networking after going through its procedure.

Can you manually boot up into Safe Mode with Networking ?
Tom.

Offline Shane

  • Lead Developer - Coder
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9279
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Not a bug. The reboot to safe mode isnt on the tabs. Look and you will see the border for the tabs, the button is outside the tabs, same as the logo.

The reboot to safe mode just calls the bcdedit command to ask the windows boot manager to set it. So it sounds like the command failed for some reason, either bcdedit was missing or the {current} value in the command didnt work like it should.

The reboot to safe mode is just there to make it easier for users to get to safe mode. The other easy way is to just use msconfig :-)

Shane