Skip to main content

Try & Decide - Mode doesn't survive WIN-Restart (WIN10)

Thread needs solution

Hi together,

I own a HP Elitebook 850 G5 and ATI2019 installed.
T&D-Mode runs well until I restart the System.

What means, that the "Blue Screen" with the decision "Continue"/"Decline" doesn't appear!
This means all changes will be deleted and I have the "old" machine.

Why does the system skip the "Blue Screen"?
I also own two other machines, Asus V3 771 and Acer ROG 752, here all thing running well!

Where can I switch on this screen?
What does prohobit this screen?

THX MbG MfD

0 Users found this helpful

Manfred, have you checked that when you enabled T&D that your computer wasn't using Windows Fast Start as this does not allow for a full restart of Windows but goes into a hybrid sleep state instead when you use shutdown & start Windows again, that can interfere with other boot options that may be set?

Hi Steve!

Uh! I didn't check this, and I have no idea in the moment where to switch on/off.
Do you mean, if I (really) shut down the PC then it should work - so that T&D will give me the "BlueScreen" to decide?

I'll try to really shut down/start today and give report.

BUT:

"One" thing, you should know: HP Elitebook 850 G5 uses something, called "SureSart". I don't know exactly what this does, but afaik it prohibits "foreign" booting or somewhat else.

I generated a system report, do you think it could help you/me?

AND:

I checked UEFI Settings of  HP Probook 850 G2 in conserns of "Secure Boot", at my other notebook (G5) called "SureStart". Please look the settings in the screenshot. Which setting does T&D need?

THX KR MfD

Attachment Size
490520-164627.jpg 266.21 KB

Manfred, I am at a disadvantage with this issue as I have never had any luck in using T&D myself and do not have any HP computers to do any testing on. 

From a brief search for HP Sure Start, this looks to be tied directly into Secure Boot in the UEFI settings and is intended to protect against BIOS changes by rootkit type malware.

I wouldn't have expected this to stop Try & Decide from showing but I guess it really depends on how strict it is in applying its criteria.  My understanding of Try & Decide is that it uses a very similar mechanism to the Acronis Startup Recovery Manager (ASRM) which would give a F11 key prompt on boot to allow Backup or Recovery actions.  ASRM uses a small Linux kernel OS (or was doing so when I last touched it!). 

It might be interesting to see if you can enable ASRM on this HP computer and test to see if you are shown the F11 Acronis Loader prompt on restarting.

Note: You can bypass Windows Fast Start by doing a Restart instead of using Shutdown, or else by pressing / holding the Shift key when clicking on Shutdown.

Oh.! I definitely used "restart" button, *not* "shutdown and start again"!

I opened a case in Acronis Support and I wonder if they will be able to solve this failure.
So this is getting more and more strange...

What exactly to do with ASRM?
Just hitting F11 during the start?
I'll check...

KR MfD

With ASRM you should see a black screen that looks like the one shown in KB 58403: Acronis True Image: How to change Acronis Startup Recovery Manager delay time and key

In essence, ASRM is a local equivalent to booting from the Linux rescue media using the HDD.

I did some testing of Try&Decide during the beta program for ATI 2018 and ATI 2019. It worked far better than in earlier versions since Try&Decide was reintroduced (ATI 2016 (?) and ATI 2017). Unfortunately the beta forums are inaccessible so I cannot give a link.

As Steve suggests, the UEFI settings of the HP probably block Try&Decide. If memory serves me correctly Try&Decide works much better with BIOS rather than UEFI.

Ian