Avast Clear Stuck At 99

[Minette Mccandrew]

Ifollowed Apple instructions to fix the hd, permissions, Terry reboot in safe mode and finally reinstalling mavericks twice. But nothing, still frozen at the grey screen with the spinning wheel and the sole logo.

I did the whole "Shift-Command-V" thing and it seems that the problem occurs with one of the boot items. It says, "BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory".

"Avast" is perhaps the worst of the whole wretched lot of commercial "security" products for the Mac. Not only does it fail to protect you from any real danger, it throws false warnings, destabilizes and slows down the computer, and sometimes or always corrupts the network settings and the permissions of files in your home folder. Removing it may not repair all the damage, and neither will Disk Utility or even reinstalling OS X.

The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.

b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.

c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.

If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.

Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.

When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.

If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)

Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.

This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.

If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.

Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.

This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.

After exhausting all options tech support could give me, they advised me to post my problem here.

I have been unable to play the game for over a month now due to a launcher bug that causes the launcher to get stuck 'analyzing files' indefinitely. I have tried reinstalling many times, have tried downloading from torrent, turning off all antivirus and firewalls, resetting my routers, turning off router security, disabling all other optional processes, running many FixIts, and anything else tech support thought to try.

The only recent changes to my computer include doing a complete factory reset a few weeks before the problem started, installing a SSHD and 8 additional GB of RAM and resubscribing to Avast and Avast VPN. The bug only began weeks after these changes and the game was working fine during that time.

Running Aces.exe produces the error 81110007.

Pack reading error 'ui/fonts.vromfs.bin'

Call stack (7 frames):

30E7CA aces! ?

30D340 aces! ?

30D257 aces! ?

FEBFAA aces! ?

769A337A ?

77C292E2 ?

77C292B5 ?

The only other thing that is weird that I noticed is that I have no launcher_udp file and it doesn't show up even after reinstalling.

No YAC.

All exception made in Avast, also have tried completely shutting down avast and doing a restart but still no luck.

Also, I have no cache file in my WarThunder folder. I'd link an image but I can't seem to add any images.

Ok, I tried deleting all the vrom files but the issue persists.

I deleted everything and ran the stand alone client outside of steam in C: and tried it in an external K: drive but it is still happening.

My last reply must not have gone through.

I tried with the new patch and I'm still having the issue. I had screenshots but I deleted them after I sent the last reply. Windows made me do a debugger and there was something with a kernel.

New DxDiag attached

I re-downloaded and now I have a cache file and a launcher_upd file which I did not have before. I'm still get the same error when I run aces.exe and the analyzer gets stuck 75% through. I tried deleting all the .vromfs files again but no luck.

Sporadically, we are seeing some of our Macs getting stuck in a boot loop. This manifests itself after the Mac has run some OS updates. In the latest case, the updates appear to be the security update 2018-001, iTunes, Safari updates. I have seen this before and I just don't understand what is causing this.

Anyone else seeing this? If you have, do you have a fix or something else I can try? Very frustrating to have this occur and we have to backup the drive, wipe the internal drive, install the OS, applications and settings and recover from the backup.

How are these Macs getting their software updates? It sounds like the update packages are getting corrupted. It's likely that the security update is the issue since iTunes and Safari don't require a reboot. I recently had a user with this problem. I booted her Mac off of an external boot drive, and I was able to go into the internal hard drive and remove the offending update files. After that, the system booted up normally.

As for us, we are simply issuing a command, software update -i -a and this has worked flawlessly in the past. I have not had any success with re-installing the OS. In all of our cases, we had to backup, reimage and restore to get the Mac back to booting.

Let me ask. We use a firmware password on all of our Macs. I wonder if this could be interfering in some way, doubtful, just curious if you are using firmware passwords too? We also have Avast installed. Perhaps Avast is interfering with things?

Hey @howie_isaacks when you mentioned, remove the offending files, how would you find those files? What folder would I look into for these? I believe it was the security update that did it, but I want to make sure where I would look for those files. Thanks again!!

We have had a few machines get stuck in an update loop.

The fix was to hold option on boot and manually select the boot drive again while holding control to set it as default (they were endlessly booting of an update image file, failing to update and rebooting of the image file again).

Re-applying the update afterwards worked fine as well so no idea as to the original cause, this was particularly bad with the 10.13.2 supplemental update.

3a8082e126