Yes I did. Also had a problem that it would boot into a desktop that was totally different from mine.
Couldn’t shut down the system always needed to do a power button shutdown.
It usually took two tries to boot into the correct desktop.
Have you tried doing a repair of Avast ???
Program and Features > select Avast > then select Repair. When the repair is finished, reboot your computer.
See if that solves your problem.
I can’t remember to be honest, but i have installed it 4 times and each time it fails to load the console and stops Windows restarting or shutting down.
Maybe i will try again tomorrow then try a repair.
If you rolled-back, you could also do a System Restore back to before you began accepting the upgrade. Then it will let you upgrade again… but FIRST, uninstall Avast
After a successful update to build 10547, I found my problem to be CryptoPrevent not Avast.
After doing another upgrade to b10547 I found that the problem most likely is not Avast.
I had totally removed Avast, stopped all programs that do any sort of scanning in the background and Reversed CryptoPrevent settings.
After the upgrade, I did a fresh install of Avast, allowed the rest of the programs to start doing their background scans and then rebooted the system.
There were no problems rebooting the system.
Next I ran CryptoPrevent to again gain the protection against CryptoLocker and rebooted the system when requested.
It took quite a while and then the flashing screens started and the system would not boot.
I did a hard restart. When I rebooted, I would up with the lock screen, managed to sign in bu the screen resolution wasn’t right.
I again rebooted and the system after quite some time finally started properly.
I’m of the opinion that the problem was CryptoPrevent not Avast.
It’s been awhile since CryptoPrevent definitions were updated. Likely this is a policy issue where Win 10 beta 10547 differs from Win 7. Have you contacted dev over at CryptoPrevent?
I use Avast Internet Security Paid version. I use the Avast firewall. I have no other conflicting apps as far as I know. I am unable to use Avast with build 10547. I was unable to install 10547 in spite of multiple attempts until I uninstalled Avast. Once it was installed, I reinstalled Avast and then all sorts of problems occurred, making the program totally unstable. I uninstalled Avast again and all was fine.
Except, I have paid for Avast and can’t use it. This must be fixed by Avast as all other programs seems to work well in this build.
Windows 10 build 10547 has all sorts of problems with Avast. As others have said, its in the fast ring so expect problems, as the core Avast program would need to be updated for the latest build or even Microsoft to fix it on their end.
Either way, if Avast means that much to you, i’d personally take yourself off the fast ring and select slow ring instead as that would release more stable versions of Windows 10 and maybe the core Avast program would be updated to reflect that.
In short, 10547 has problems with Avast, save yourself the headache, either dont use Avast for that build or dont upgrade your PC to that build.
As requested, I rebooted the system.
The system restarted with a white screen that flashed a few times and then showed the
Windows 10 Lock screen. (My system was set to bypass the lock and sign-in screen.)
My settings still showed that a password was NOT required.
I checked the box to require a password, then unchecked it again and hit apply.
At that time I was asked to enter my password and confirm it.
Once applied, things were back to normal.
No problem with rebooting!
OK I am going to run for a day and if it starts becoming unusable again Avast will have to go…
At the moment both IE and Edge are unusable and I am being forced to use firefox
In IE on any forum I am unable to click any hyperlink for subforums, I just go somewhere random like member profiles. It is the same with or without AOS enabled
I will be doing some reboots to see if the white flashing screen returns and reboots hang for one or two minutes after pressing shutdown
Attached is my event viewr during the period whilst I was trying to get the system to boot, the time when Avast was not installed was nice and clean
The referenced files are dmw.exe and ntdll.dll in all cases. So Avasted is doing some interfering there