Boot time scan does not work

Hello,

Moment I am clicking on the start button against the boot time scan selected in the scan dropdown, i get an error. It says

Unable to start scan
The IOCTL call made by the application program is not correct.

Kindly help as how can I get the boot time scan to work.

Thanks

It is a real good practice that if you want help to provide at least some details.
Telling a mechanic “there is something wrong with my car” is not really helpful. :wink:

What OS/SP ?
What exact version of avast ?
Any other security (related) software installed ? (or was there)
Already performed a repair of avast ?
Already did a clean installation of the latest avast ?

Sure Eddy, my bad.

Windows 8.
Avast - 10.4.2233
No other security software
Not performed repair of avast yet
Old installation of avast and is upto date.

Update to the latest version (2016.11.1.2241): https://forum.avast.com/index.php?topic=178580.0

Getting same error as above.

Unable to start scan
The IOCTL call made by the application program is not correct.

Will not start any scan. Using Windows 7 x64 with Avast Internet Security ver 2245.
No other security software
Tried program repair thru control panel. No change
Did clean install. No change

Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle

Not sure this will help as there was apparently no confirmed solution posted:-

https://forum.avast.com/index.php?topic=153614.0

Whatever that ^ fix it program is, and I expect in this case it is recommended from personal experience and use, if I had come across it anywhere else I would have been suspicious.

It does not look like an official MS tool and the name of the site, suggesting that it might be, immediately raises concern.

Is it anything more than another of those “system optimisers”? At best they do little more than run CHKDSK, defrag, file clean, maybe an AV/AM scan included too and sometimes driver update. At worst they’re little better than malware themselves installing who knows what and stuff up your sytem.

Update to ver 2253 fixed problem. Thanks

OK, thanks for the feedback.