![]() ![]() I'm still not ruling out an error or glitch, but there doesn't appear to be a problem with the hardware. I was starting to worry that my internal flash memory had failed. The Applications folder opened just fine. I had what was essentially a fresh machine. Google Nexus 6 review: A larger Moto X with fewer Motorola enhancements I did a fresh install of Yosemite (because the Recovery Console, apparently, won't recover earlier OS versions) and rebooted. I selected my internal flash storage and hit Erase. Next, I took a deep breath, rebooted into the Recovery Console, and launched Disk Utility. Unfortunately, the Applications folder and system problems also remained. The restore completed successfully, keeping all my settings and applications in place. I tried to do an OS restore without zeroing my flash storage. It was time to go old-school on the problem.įirst, I rebooted, holding down Command and the "R" key to go into the Recovery Console. In any case, none of the recommended fixes fixed the problem. I was not, however, experiencing this problem on a Retina machine (which many of the forum posters thought was a common symptom), so that wasn't a match. I was also running Creative Cloud (two applications many of the troubled users found to be using in common), so I made sure to turn them off. I dutifully followed the various recommendations without success. In particular, I found an Apple support forum filled with discussion on this exact issue, along with discussions about how to fix it. I did a Google search on "yosemite applications folder empty" and turned up a relatively active list of results. The problem didn't go away, so I went online. ![]() But as it turns out, those permission fixes didn't stick, because subsequent Disk Utility runs found those same permission errors and fixed them again. Disk Utility found some permissions incorrect, and fixed them. The very first thing I did was launch Disk Utility and run some disk checks and repair sweeps. I was also experiencing other application-related failures (like some maintenance tasks weren't running). I launched Terminal and was able to do an "ls" and see all the applications. But if I tried to move an application into the Applications folder or look at the contents, nothing. If I tried to run an application by using an existing Dock item or shortcut, it would run. All of a sudden, I couldn't see any applications in my Applications folder. Unfortunately, shortly after upgrading, my machine became unusable. I considered that I might as well upgrade and make sure everything was configured right, before adding those products into the mix.Īll are good and fair reasons. So, this last 24 hours of pain-in-the-butt has been all for you! You're welcome.įinally, I'm about to get started on a big project that will require loading a pile of new software. ![]() I write about new technology and if I don't eat my own dog food, I won't be able to tell you about my experiences. ![]() These naggings were interrupting my flow and my thinking was that since I hadn't heard many complaints about upgrading to Yosemite, I might as well just do the deed. It's incredibly annoying to get an upgrade notice from Parallels, for example, every time you need to launch a Windows VM. The biggest is that a number of the Mac applications I use every day have started to nag me with upgrade notices, even while running on Mavericks. I upgraded to Yosemite for a few reasons. Then, a day or so ago, I moved to Yosemite. I started it on Mountain Lion, waited until Mavericks seemed to have most of the kinks worked out of it, and then moved to Mavericks. Until this hard crash, I've been surprisingly satisfied with the machine. I've told you a lot about the heavily configured non-Retina iMac that I bought just about 13 months ago. How to decide if it's time to upgrade to OS X Yosemite Using Parallels in Coherence mode on a four-monitor iMacĪfter all this time, how can OS X Mavericks STILL be this bad?ġ0 great apps too powerful for the Mac app store Making it work: Four displays on a monster iMac Open letter to Tim Cook: it's time to call Mavericks beta Why I chose a maxed-out iMac over a powerful PCįrom Mavericks back to Mountain Lion: so much for that plan Why I bought a tricked out iMac instead of a Mac Pro Maxed-out iMac: just how far can we push this thing? That is, until last night, when my machine crashed right after I upgraded to Yosemite. Back in October, Wi-Fi problems, we haven't heard all that much about Yosemite being a nightmare. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |