2015.10.3.2223 and Macrium Reflect 6 Free possible conflict on boot?

YLAP · 2015-07-13T07:31:28.000Z

Hello,

yesterday I played a bit with avast. Did clean 2218 install and later that day upgraded it to 2223. I’ve noticed one possible conflict maybe. I am using Macrium Reflect 6 Free, latest version. It has an ability to add a recovery menu to the boot. Simple, it just ask boot to Windows or you can choose some recovery options. It has a timer, so it counts the time till the Windows is booted. With 2218 it works fine when turning the PC on or restarting it. When 5 seconds set by me is gone - Windows is loaded. With 2223 I’ve started to encounter some problems. During the restart the countdown timer of Reflect boot menu works fine, during cold start - timer is gone after about 2 sec and the system is not booting until I choose manually what to boot. Maybe someone is using Macrium and encountering similar behaviour? Because of this I’ve tested again it with non beta version of avast, so I know this came after BETA was installed. Maybe something at the boot is not friendly with Macrium Recovery Boot Menu.

DavidR · 2015-07-13T15:08:28.000Z

This could well have a larger impact since the 2015 10.3.2223 R3 RC2 beta build. Now that the Release version is the same build as the previous build it will find many more macrium reflect users.

YLAP · 2015-07-13T15:14:48.000Z

DavidR post:2:

This could well have a larger impact since the 2015 10.3.2223 R3 RC2 beta build. Now that the Release version is the same build as the previous build it will find many more macrium reflect users.

LOL, strange move from avast side ;D Because I am stuck on beta till the next beta as my beta says it is up to date and does not understand it is not beta anymore And yes, you are right. I think we will know soon if I am the only one with a bug on Macrium or not

system · 2015-07-13T16:41:35.000Z

I have not noticed this in Windows 7 with MR 708. If I do, Avast will be removed.

Lisandro · 2015-07-13T17:56:18.000Z

Ylap, I haven’t noticed any change in my Macrium boot option and the counter…

YLAP · 2015-07-13T18:02:52.000Z

Lisandro post:5:

Ylap, I haven’t noticed any change in my Macrium boot option and the counter…

Hmm. My went crazy as soon as 2223 was installed back on PC. It just not finishing countdown on system start (strange, but no problems upon restart). Not critical thing, I can choose option manually. Yet it seems it may be more than just avast and Macrium, it may be some kind of software combination on my notebook or even BIOS related thing. Seems it is not a widespread bug, it is my local misbehaviour

Lisandro · 2015-07-14T01:05:53.000Z

=YLAP= post:6:

Hmm. My went crazy as soon as 2223 was installed back on PC.

I was talking only about Macrium.
I have to recover a full PC image when I’ve installed 2223. It was a nightmare…
https://forum.avast.com/index.php?topic=173501.0

There, nobody posted nothing… Well, what a fantastic return for a beta program

kolar · 2015-07-21T12:29:16.000Z

Hi guys,

I’ve tried to reproduce this problem on Windows 8.1 x64 and Windows 7 x64, however, with no luck. The only way how to stop the counter is when I move my mouse which happens normally… Could you provide any additional info?

YLAP · 2015-07-27T19:21:34.000Z

Well, at least you gave me one idea to check. I will try to turn off my Bluetooth mouse to see if it makes any difference. Maybe when mouse connects to the PC it is taken as movement… Or it may be touchpad. I don’t know, but my counter still misbehaves on cold start

Huh. No go. 5, 4, 3 and timer is gone Nothing touched, nothing moved. Mouse off. Maybe it is device specific problem and even vendor bug related, not avast, as my notebook also sometimes likes to freeze keyboard and touchpad completely. Thanks good touchscreen is working in this scenario, Bluetooth mouse too, so I can turn off PC. Restart does not solve frozen hard keyboard and touchpad. At this moment it sounds like a driver problem or conflict, I don’t know. Yet it is another mystery for Scooby Doo to solve

YLAP · 2015-08-15T11:45:17.000Z

Well, the problem is clear now. It is my Bluetooth mouse. Then it connects it gives such a behaviour

Announcements