Avast For Mac Won't Install Stuck At Installing Scripts
Mac OS X Lion is easier to install than any previous version of Mac OS X. You don’t have to boot from a DVD or flash drive. Just download the Install Mac OS X Lion app from the Mac App Store and let it walk you through the remaining steps.
I just downloaded Office 365 for Mac, and tried to install it in macOS Sierra 10.12.5. The installation froze when Running Package Scripts. It is a common problem. Installation of Office 365 for Mac is freezing at “Running Package Scripts” (Sierra) Ask Question.
Still, things can—and occasionally do—go astray.
Installation of Office 2016 or Office 2013 hangs at 90%. If you've already cancelled Office install, try installing Office again. For reinstall instructions, see Install Office on your PC or Mac. If you haven't quit the installation, use Task Manager to end the Windows Update process. Just purchased Office 2016 for Mac via download. Trying to install; stuck on 'Verifying 'Microsoft_Office_2016_Installer.pkg' for 2 hours now. Find all PC and Mac installation files for AVG antivirus, VPN, and tuning app in one place, including the latest updates, and trials. Activated with the wrong license. If you own multiple licenses and have installed using the incorrect one, or you had a one-time install of Office for Mac and then purchase Office 365, you might need to remove licenses attached to your suite of Office and reactivate to ensure you're getting all the benefits of Office 365. How to Install Java in OS X El Capitan. And you can also avoid installing java. Mac users may need to disable rootless SIP protection in OS X before being able to successfully install Java, but you can enable it again after it has been installed. If you get stuck on “verifying” during the installation process of. Unless you do a custom install, Avast will automatically install everything. Avast has progressively gotten more bloated, more laden down with 'features', and progressively more uncaring of the user's system by adding stuff to it that is detrimental to the end user.
One possible hitch right away is that you’ll need to have the Mac App Store application on your drive. This requires that your Mac be running OS X 10.6.6 or later (for more help on this and everything else you need before you can install Lion, read Dan Frakes’ Lion installation guide, particularly Get your Mac ready for Lion).
Assuming you pass this hurdle, the next place where things may go wrong is during the installation process itself. In particular, you may get one of several warning messages.
Install app warnings
This disk cannot be used to start up your computer
Apple offers no explanation as to why the installation may balk here, other than to say it can happen in “some situations.” However, Apple does provide a solution: Restart your Mac, launch Disk Utility and, from the Partition tab, slightly reduce the size of your startup partition (by as little as 128MB). You should now be able to install Lion. When done, you can restore the partition to its previous size. If this resizing trick fails, you will likely need to reformat the drive.
This disk is used for Time Machine backups
This message again means that the Lion installation will not successfully complete. The message can appear even though your startup drive is obviously not acting as a Time Machine backup. As covered in an Apple Support Communities thread, the likely cause is an errant Time Machine-related Backups.backupdb folder at the root level of your drive. This folder, created by and used by Time Machine, is fooling the Install app into thinking your startup drive is actually a Time Machine backup. The solution is to delete the folder.
Some features of Mac OS X Lion are not supported for the disk (volume name)
If this message pops up, you’ll still be able to install Lion. However, as explained by Apple, the installer won’t be able to create a Recovery HD partition. Recovery HD is used for performing “emergency” options, such as reinstalling Mac OS X or running Disk Utility. While you can install and run Lion without this partition, ideally you want to have it. Aside from its troubleshooting value, it’s required if you want to use File Vault 2.
This error can occur if your startup drive is a RAID volume or has a “non-standard” Boot Camp partition. If you have a RAID setup and want to keep it, you have no choice but to forgo Recovery HD on the drive. If Boot Camp is the cause, the solution is to reformat your drive as a single partition. Next, reinstall Snow Leopard followed by an update to Lion. Now run Boot Camp Assistant to create a Boot Camp partition. Lastly, restore your remaining data from backups.
If you can’t or don’t want to reformat, an alternative is to install Lion on an external drive. If you ever need to boot from Recovery HD, you do so from the partition on the external drive.
Install failed. Mac OS X Lion couldn’t be installed, because the disk (volume name) is damaged and can’t be repaired. Click restart to restart your computer and try installing again.
If you see this unwelcome message, chances are slim that trying again will lead to success. The same is true if the Install application simply stalls before completing. Some users report that “zapping the PRAM” is sufficient to get past this roadblock. Otherwise, according to an Apple Support Communities thread, the fix is to boot from a Snow Leopard Install disc/drive and select to Repair Disk from Disk Utility. Assuming repairs are successful, try the Lion installer again.
Otherwise, if nothing here has any positive effect (and assuming the drive itself is not physically defective), the solution is to reformat the drive and start over.
Internet connection lost
Although not likely, you may lose your Internet connection after an otherwise successful install of Lion. If you use Avast’s Web Shield, the solution is to uninstall avast!. There is a known conflict between Avast and Lion. As posted in an Avast forum thread, a supposed bug-fix update, still in beta, is available. In this same thread, the company lays the blame on Apple: “Packet forwarding is broken on Lion. Lion either does not redirect the packets (your case) or crashes. This bugs have been reported to Apple long time before the Lion release, but it is still not fixed by Apple.”
If you don’t use Avast, a more general potential fix is to turn off the Mac OS X Lion Firewall (in Security & Privacy System Preferences), and delete the firewall-related com.apple.alf.plist file in /Library/Preferences (via Terminal if needed). After a restart, you can re-enable the Firewall.
Redownload Lion?
For installation failures that could be due to a corrupt copy of the Install Mac OS X Lion app, you should redownload a fresh copy of the app and try again. However, if a copy of the Install app remains on your drive (which is likely if you have been unable to complete a successful install), the Mac App Store will claim that Lion is “Installed” and will not permit a redownload. In fact, it is likely to make this claim even if you have never attempted to install Lion after downloading the Install app.
To work-around this, delete the the Install app. Next, from the Mac App Store app, hold down the Option key and select the Purchases tab. You should now see the Install Mac OS X Lion app listed with a download option enabled.
Editor’s Note: Due to a production error, we posted a shorter version of this article earlier on Friday. We’ve updated the original article at 2:17 p.m. PT with even more troubleshooting details on Lion installation.
Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Aug 3, 2016
Please use the following bug reporting template to help produce actionable and reproducible issues: Install bash hangs when 'init' is executing using a full core but no visible activity You can 'successfully' end the installation, but then each attempt to run bash will just result in init spinning forever |
commented Aug 3, 2016
I'm having the exact same issue. I've gone through the correct steps to install Bash. I'm 100% sure about that. The install hangs at 'Extracting filesystem' with the init process showing up in task manager. I've tried installing via 'bash' in the start menu as well as with |
commented Aug 3, 2016
I am also experiencing the exact same issue. |
commented Aug 3, 2016
I am also experiencing this issue. I left my command prompt at 'Extracting filesystem..' overnight and it did not complete. |
commented Aug 3, 2016
Did any of you made a clean install of Anniversary Update? Avast Pro Antivirus 2017 Crack Mac 18.4.3895 + License File Full Setup May 29, 2018 May 29, 2018 Cracked Only Avast Pro Antivirus 2017 Crack is a member of internet security family developed by Avast Software supported with Microsoft Windows, MacOS Android & IOS. Avast 2017 free download - Avast Free Mac Security, Avast Passwords, Avast SecureLine VPN, and many more programs. Avast Free Antivirus. VirtualDJ 2018. Avast Security Pro. Detect viruses. Avast Pro Antivirus 18.4.3 + license key Latest Version November 9, 2018 Anti-Virus, Full pc software free download, Windows 0 77 avast pro antivirus license key is a very powerfull software for windows operating systems likes Android, Windows, Linux, and Mac OS X. Avast Pro Antivirus (2017) v17.1 License Files –is a pc programming which is controlled with antivirus and hostile to malware assurance. It has extra components for the individuals who are not anxious of details. Avast Pro Antivirus: is a pc programming which is controlled with antivirus and against malware security. /avast-antivirus-pro-for-mac-torrent-file-2017.html. |
commented Aug 3, 2016
I did a windows update (from a previously fully updated windows 10 version), not a clean install. |
commented Aug 3, 2016
I have run into the same problem. Previously I tried installing Bash on Ubuntu on Windows using the Bash command in Command Prompt. The installation got stuck at 'Extracting filesystem, this will take a few minutes..' but only after a restart, as the bash process was still running and killing it from PowerShell gave Access Denied exception. I only have Windows Defender as my antivirus program. |
commented Aug 3, 2016
Relatively fresh install of Windows 10 Pro, windows update installed the Anniversary Update yesterday, which necessitated a series of reboots. I have disabled all antivirus protection (Avast) and turned off malwarebytes also. LocalAppData and AppData are not symlinked and in their default locations. While it says 'extracting filesystem' there is an 'init' process owned by my user taking 10-20% CPU time. |
commented Aug 3, 2016
Oh, and I'm joined to a test domain, but I am logged in to an account with local administrator and domain administrator access to test this. |
commented Aug 3, 2016
I didn't do a clean install, just an update. I'm running Avast, but I've tried disabling it without any luck. As for messing with AppData and LocalAppData, I haven't done anything to them. My init process is also running at about 10-20%, but nothing happens. |
commented Aug 3, 2016
Avast here, I also tried to deactivate it, no change. On Wed, Aug 3, 2016, 13:54 onomatopellan notifications@github.com wrote:
|
commented Aug 3, 2016
A RamDisk or Virtual drive could affect the install, disable them if you have one. There is a known problem with having more than one pagefile. #565 It could also be related to this new unsolved bug. #707 |
commented Aug 3, 2016
I've only got one pagefile and I don't have any virtual drives or RAM disks set up, so that shouldn't be an issue on my end. |
commented Aug 3, 2016
Avast For Mac Won't Install Stuck At Installing Scripts In Firefox
It seems #707 is now solved. Did you try looking for the reg entry? |
commented Aug 3, 2016
I just updated a Win 10 Pro machine and everything went smoothly, I didn't even had to enable developer mode - it did it for me. Is there an issue with Home edition |
commented Aug 3, 2016
It was already set to 1, yeah. I should note that there is not an error message like in #707. The install just hangs indefinitely. |
commented Aug 3, 2016
If you WIn+R and go to %localappdata%/lxss what do you see? Can you enter on rootfs directory and see its contents? |
commented Aug 3, 2016
I can enter lxss/rootfs, yes. It contains multiple folders as well as the 'init' file. |
commented Aug 3, 2016
If you didn't see any lxxs.tar.gz file on lxss folder then it means it extracted the files correctly, deleted the lxxs.tar.gz file and then it hangs. |
commented Aug 3, 2016 • edited
edited
@onomatopellan thanks for helping folks out. To clarify WSL does not require the obcaseinsensitive registry key. We enable case sensitivity temporarily on a per-thread basis for pico processes that are running Linux binaries. @JacobStearns do you happen to have a third party firewall installed? We've seen the install hang for users using Kaspersky and Bitdefender firewalls because they are blocking the network traffic of our pico processes. |
commented Aug 3, 2016
@onomatopellan Just to confirm, there was no lxxs.tar.gz, so that should all be fine. I'm running @benhillis I do not. I'm running Avast free, but that doesn't contain a firewall. I've tried disabling Avast, but that doesn't seem to help at all. |
commented Aug 3, 2016
@JacobStearns, I have exactly the same issue and the same behaviour after executing the And I have the same content than you in the rootfs directory. AND I have running (but disabled) the free version of Avast.. Pretty similar. |
commented Aug 3, 2016
BTW, I have only one pagefile Another question, do you have some kind of software like NoMachine Nx server installed? |
commented Aug 3, 2016
@salvavn Can confirm, this is the exact behavior I'm seeing. |
commented Aug 3, 2016
@salvavn I do not. |
commented Aug 3, 2016
It seems like lots of guys with the same issue have Avast working.. I don't know if it's only a coincidence.. |
commented Aug 3, 2016
Could you try uninstalling Avast, restarting Windows and then trying bash again? |
commented Aug 3, 2016
Can do. I'll be back once that's done. |
commented Aug 3, 2016
Success! I have removed Avast. Then I have uninstalled bash with After that, I have rebooted Windows. And then, I have installed the linux stack with: And it works! Now the prompt has asked me for the user name and password. |
commented Aug 3, 2016
I'm going to install Avast again in order to check if there is some kind of interaction after the bash installation. |
commented Aug 3, 2016
Hey guys, bad news. I was executing in my bash prompt the So, in my opinion, the current AVAST version (the latest one) is incompatible with bash. :( |
commented Aug 3, 2016
Uninstalling Avast fixed it on my end as well. It's unfortunate that Avast seems to completely break Bash. |
commented Aug 3, 2016
I have tried disabling Avast, but didn't work. The only way I'm able to work with bash is with a full deinstallation of Avast :( |
commented Aug 3, 2016
I can confirm the problem is Avast (unfortunately, I found this issue only after spending a couple of hours before figuring it out myself..) The problem also occurs with Avast's free Business Antivirus version. It's not enough to turn Avast's shields off; the product has to be uninstalled. |
commented Aug 3, 2016
It seems Firewalls and AV will have to be updated to support the new picoprocesses. |
commented Aug 3, 2016 • edited
edited
Anyone having recommendations for AVs that are compatible with Bash? Webroot seems to work just fine. In fact I am pretty annoyed by Avast because it broke things because of false positives, adding a message to each outgoing mail .. good opportunity to ditch Avast for good I moved to Bitdefender on the machine that showed and it fixed it. |
commented Aug 3, 2016
Disabling the AVs may not be enough. Uninstalling it is a good way, but how about 'closing' the AVs temporarily? |
commented Aug 3, 2016
I had to uninstall Avast for it to work at all. As soon as I reinstalled Avast after installing bash, I couldn't actually run bash anymore. I was in the market for a new AV anyway, may as well test out Defender. |
commented Aug 4, 2016
@salvavn It worked like a charm, uninstalling avast did the trick Thanks |
commented Aug 4, 2016
Glad to hear. To keep everybody in the loop I've been reaching out to third party firewall providers and will work with them on getting this fixed. Thanks everyone for trying WSL! |
commented Aug 4, 2016
here is another issue who deals with 3rd party firewalls. |
commented Aug 5, 2016
Thanks for working on this. |
commented Aug 5, 2016 • edited
edited
After reinstalling Bash a couple of times.. and waited till it hung at the extraction stage. After a couple of hours, I simply closed the command prompt. Task manager showed bash running. The lxss folder didn't have the tarball, which probably means everything was extracted correctly. I realized I had multiple page files. So I set it to 'Automatically manage paging file size for all drives', then rebooted. I also disabled Windows Firewall and turned real time protection off in Windows Defender. I do not have any other Antivirus installed, Then ran It worked. I then created a new for me |
commented Aug 5, 2016
Glad it worked for you. |
Adobe Flash Player For Mac Won't Install
commented Aug 21, 2016 • edited
edited
To me it seems that the current newest version of Avast Free Antivirus (12.3.2280 / build 12.3.2154.0) does not have this issue. Installing WSL hanged on the 'Extracting filesystem' part, but then I updated my Avast av and after that, installing WSL got past that to a successful installation. |
commented Aug 21, 2016
It's working on my end, too. Bash and every program I've tested have worked with Avast so far. If there's any issues still present, I haven't found them. |
commented Oct 6, 2016
Hi all, I just wanted to give my two cents on the Avast business. Bash.exe had been working perfectly fine for me and has with minimal problems since it was first released. A little while ago, I tried to move a big directory into another directory and it got hung up. It remained hung up after trying to Ctrl-Z it into the background or Ctrl-C it out of existence. So I closed it out. Opening it again, it remained hung up. Restarted; still hung up. Ultimately what appears to have fixed it is permanently turning off Avast's File System Shield and then restarting. After the reboot, bash became unhung! Then I could just turn on the File System Shield again. Avast Settings > Components > File System Shield Off > Stop Permanently TL;DR |
commented May 23, 2017 • edited
edited
Malwarebytes For Mac Won't Install
Avast supports exclusion path, adding the lxss path:
Maybe this can stop Avast messing up files for WSL ? |
commented Jun 27, 2017 • edited
edited
Having a similar issue here. No Avast involved though. Tried to install bash and it hung on I miss my mac. edit: and now |
commented Jul 12, 2017
This should be resolved in Creator's Update. If others are experiencing this same issue in Creators Update or later, please let me know! |
added the fixedincreatorsupdate label Jul 12, 2017
commented Nov 22, 2017
having the same problem here. im not running Avast but have something called f-secure (it's called kpn veilig idk why). tried to run bash anyway. it worked before i used any commands. i used ls and the system freaked out and then outputted the right thing for some reason. the file location seems bugged to but but works anyway. it seems like it now only has weird visual bugs. i hope this information can help find where the installation stops. |