Permissions on folders damaged - Finder crashes on changing

On two upgraded Macs I find that the user home folder and various sub-folders under it have permissions messed up. All folders except some of the special, pre-defined, folders such as 'Pictures', 'Music', 'Library' etc.
What shows is:
UserName (Me) - Read & Write
(unknown) - Read only
everyone - Read only
I suspect that the '(unknown)' entry is what used to be the group for UserName which has not been properly transferred to Leopard.
Also if you try to edit/add any the permissions Finder will crash.

I'm having the same problem!
here's the the log I get when doing repair permissions:
Permissions differ on "sbin/restore", should be -r-xr-xr-x , they are -r-sr-sr-x .
Warning: SUID file "sbin/restore" has been modified and will not be repaired.
Permissions differ on "sbin/rrestore", should be -r-xr-xr-x , they are -r-sr-sr-x .
Warning: SUID file "sbin/rrestore" has been modified and will not be repaired.
Permissions differ on "sbin/launchd", should be -rwxr-xr-x , they are -rwsr-xr-x .
Warning: SUID file "sbin/launchd" has been modified and will not be repaired.
Permissions differ on "sbin/mount_smbfs", should be -r-xr-xr-x , they are -r-sr-xr-x .
Warning: SUID file "sbin/mount_smbfs" has been modified and will not be repaired.
Group differs on "usr/bin/lppasswd", should be 0, group is 26.
Permissions differ on "usr/bin/lppasswd", should be -rwxr-xr-x , they are -rwsr-xr-x .
Warning: SUID file "usr/bin/lppasswd" has been modified and will not be repaired.
Permissions differ on "usr/bin/smbutil", should be -r-xr-xr-x , they are -r-sr-xr-x .
Warning: SUID file "usr/bin/smbutil" has been modified and will not be repaired.
I really can't do much in finder at all.
Message was edited by: corn

Similar Messages

Finder crashes when changing folder permissions

When I try to change a folder's permissions via the Information window (Apple + i) the finder crashes reproducably.
This is what I do:
1.) select folder in finder and press apple + i
2.) click the lock icon and enter Admin name and password
3.) select "everyone" in name column
4.) click on rights in the rights column
5.) spinning ball, finder crashes and restarts
According to http://docs.info.apple.com/article.html?path=Mac/10.5/en/8342.html
steps 1 through 4 are exactly what should be done.
Any other ideas?
PS: I can remove users/groups via the +/- buttons but clicking the activity (is that the name?) button next to it leads to step 5.

Then, I surmise that the problem's system-wide. For that, install the 10.5.5 COMBO update, repair permissions, and restart. If that doesn't fix things, you're looking at doing an Archive & Install installation. Details at http://support.apple.com/kb/HT1545

Permissions modification makes the finder crash

My folders have user lists of "Me", "(unknown)", and "everyone", with the default permissions set to "Read & Write", "Read Only", and "No Access" respectively. When I click the little "+" button to apparently add another user to the list the finder restarts after a small pause. Additionally, if I select the "everyone" group or the "Me" user and click the "-" button nothing happens. Furthermore, I cannot change the "(unknown)" category at all. Usually there are "User", "Group", and "Everyone" categories, or at least thats been the case with pre-10.5 versions of OS X. I have repaired the disk's permissions but it hasn't changed anything. Any clues?

http://docs.info.apple.com/article.html?artnum=307128

Finder crashes when scrolling in a large directory

I came across a weird problem today on a clients power mac (OS 10.4.11)
They have a large directory (~200 sub folders) and when you scroll down the list of sub folders the finder crashes when you get the the "N"s
It looks a lot like when explorer crashes in windows (everything is gone minus the background and eventually the icons and start menu reappear) except this version just happens a lot faster
I did some research and people were saying that deleting the com.apple.finder.plist files and rebooting fixed it but that did not work with me
anyone see this before?

I haven't seen that but I don't have a folder with 200 folders inside. I do have a folder with 9000+ files inside with minor Finder issues, but not the one you see.
Additional computer information for the client's computer? How much RAM on the computer? How much free space on the computer's hard drive?
What happens if you try to jump to, say, the W folder by typing the letter W?
Have you verified the drive with Disk Utility? Possible directory corruption.
Reading
[Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
[Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
[Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]

Finder Crashing When Opening Folders Containing JPEG Images

Here's my odd problem.
Finder seems to work okay until I open folders with certain JPEG images in them. Specifically, it seems to crash whenever I open a folder that has images taken with my old Oregon Scientific camera. It gets a little bit annoying, because once I open the folder, Finder crashes... and then it re-launches, +with the problem window still open+... which causes it to crash immediately upon re-opening. And then it re-launches again, again with the same window open, which causes it to crash again, and on and on into the night.
Incidentally... these images also seem to crash Preview. I never had any problem with this before. They worked fine under 10.5, they worked fine under 10.4... they even work fine on OS9. I've tried turning off icon previews, I've tried list view and icon view and coverflow and all that, and it crashes every single time.
If I use GraphicConverter to re-save the images WITHOUT the EXIF data, then Finder seems to be okay. But considering I have nearly a thousand images that were taken with that (decidedly unsophisticated) camera, it's really an inconvenience to convert every single one. On top of it, I'd kind of like to keep my EXIF data where it is.
I'm really kind of starting to regret not waiting for 10.6.1 before installing, because I've encountered problem after problem... and my fiance's iMac is almost unusable, it's so buggy. Most of the issues I've encountered I can live with, at least long enough for Apple to release an update... but this Finder issue is killing me, because I can't even access my photos.
Anyone have this same issue, or some idea of how to fix it?

I've duplicated this behavior on both my MacBook and my fiance's iMac, which are both running 10.6. With my 10.4-enabled G4 and iMac G3, there's no problems.
I think I've at least figured out the actual cause. I just opened a folder of pictures taken with my Oregon Scientific DShot II camera, and it didn't crash the Finder, nor did it kill Preview. The EXIF data was intact. The difference was that with these images, I'd edited them and re-saved with GraphicConverter when I first took them.
After repeating the tests with some other pictures, I think that the problem isn't so much with the EXIF data as it is with the +preview image+. The DShot II camera saves some kind of a preview image (which isn't very good). When I edited these images with GraphicConverter, the application added it's own custom preview, overwriting the original.
For some reason, Finder (and Preview, though I don't know why) handle GraphicConverter's preview image, but can't seem to be able to deal with the preview image that the DS2 embedded into the image. Why this should change with 10.6, when all previous versions of the software worked perfectly fine, I have no idea.
AJH

Finder crashes opening HD or folders

More often than not when I try to open a window by opening the HD or a folder, the finder crashes (icons on desktop go blank then return with no open folders). I tried a safe mode restart to see if it was one of the start up items, but that did nothing. The strange thing is that I'm not having the problem with the other user/account on the mac. All this is fairly recent as is my upgrade to Snow Leopard.
I tried reloading 10.6.3, but no luck. Any ideas?

My situation is somewhat similar with one important difference: my Finder doesn't 'crash' as such, but my problem is temporarily resolved with a Force Quit of the Finder (which then relaunches itself).
Here are my details: Beginning my upgrade to SL, I did a partition-Initialization>Clean Install>Update to 10.6.3 of SL (from 10.5.8) and noticed immediately that randomly-chosen directories below the top-level on my new install, as well as my NAS, when opened would appear to be empty. Top-level directories and files appear, but opening a top-folder never shows contents. The circling indicator at the bottom-right of windows continue to spin ad infinitum, but no contents inside a directory appear. Rebooting SL would reveal folder contents, but the next, or following attempt to open another directory would inevitably show itself as empty. Doing a Safe Reboot didn't change this behavior, so it appears to be a Finder issue.
After awhile I realized just relaunching the Finder would reveal anything that first appeared to be empty, so that has been my temporary workaround while reinstalling/migrating files/apps from my old volume to SL. Once revealed, directory contents remain in view, until the next reboot, when it may (or may not) show itself as empty again. Alias' that reach into 'invisible' directories remain active, either launching a file/app or opening a directory (which would, again, show no contents).
Something isn't right, but it isn't killing me. I've googled and searched here but haven't found anything that exactly duplicates my symptoms, though this thread comes closest, which is why i'm posting here.
Any thoughts?

Finder crashing in Sharing & Permissions

When trying to add a new user (clicking on the +) in the Sharing & Permissions section of the Info window for a program, I find that Finder crashes every single time, with the following :
Process: Finder [140]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Identifier: com.apple.finder
Version: 10.5.1 (10.5.1)
Build Info: Finder_FE-6070100~2
Code Type: X86 (Native)
Parent Process: launchd [73]
Date/Time: 2007-12-13 17:15:27.306 +0000
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000008
Crashed Thread: 0
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x95aec2eb CFUUIDCreateString + 43
1 com.apple.finder 0x0028692e 0x1000 + 2644270
2 com.apple.finder 0x0024292d 0x1000 + 2365741
3 com.apple.finder 0x001bb438 0x1000 + 1811512
4 com.apple.finder 0x0005af84 0x1000 + 368516
5 com.apple.finder 0x000261fa 0x1000 + 152058
6 com.apple.finder 0x0002607a 0x1000 + 151674
7 com.apple.finder 0x0002603e 0x1000 + 151614
8 com.apple.HIToolbox 0x91506863 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
9 com.apple.HIToolbox 0x91505c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
10 com.apple.HIToolbox 0x9152208e SendEventToEventTarget + 52
11 com.apple.HIToolbox 0x91556c9d SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 411
12 com.apple.HIToolbox 0x915c6004 SendHICommandToTarget + 58
13 com.apple.HIToolbox 0x9163d05c SendControlCommand(HIView*, unsigned long, unsigned long) + 64
14 com.apple.HIToolbox 0x9157c346 HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 122
15 com.apple.HIToolbox 0x915e6484 HIView::ClickInternal(CGPoint const&, unsigned long, void ()(OpaqueControlRef, short), OpaqueEventRef*, bool) + 254
16 com.apple.HIToolbox 0x915d2c96 HIView::ClickSelf(OpaqueEventRef*) + 370
17 com.apple.HIToolbox 0x91514ab1 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2391
18 com.apple.HIToolbox 0x91506863 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
19 com.apple.HIToolbox 0x91505c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
20 com.apple.HIToolbox 0x9152208e SendEventToEventTarget + 52
21 com.apple.HIToolbox 0x915d02af HIView::Click(OpaqueEventRef*) + 329
22 com.apple.HIToolbox 0x915d0111 HandleClickAsHIView(OpaqueWindowPtr*, OpaqueEventRef*) + 151
23 com.apple.HIToolbox 0x915cfa9d HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long, OpaqueEventRef*) + 505
24 com.apple.HIToolbox 0x915cf88f HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 791
25 com.apple.HIToolbox 0x9158afca StandardWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 96
26 com.apple.HIToolbox 0x91506863 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
27 com.apple.HIToolbox 0x91505c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
28 com.apple.HIToolbox 0x91577df1 CallNextEventHandler + 95
29 com.apple.finder 0x00031587 0x1000 + 198023
30 com.apple.finder 0x0008092d 0x1000 + 522541
31 com.apple.finder 0x0004476b 0x1000 + 276331
32 com.apple.finder 0x000261fa 0x1000 + 152058
33 com.apple.finder 0x0002607a 0x1000 + 151674
34 com.apple.finder 0x0002603e 0x1000 + 151614
35 com.apple.HIToolbox 0x91506863 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
36 com.apple.HIToolbox 0x91505c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
37 com.apple.HIToolbox 0x9152208e SendEventToEventTarget + 52
38 com.apple.HIToolbox 0x91534b73 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1211
39 com.apple.HIToolbox 0x91506c1c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2134
40 com.apple.HIToolbox 0x91505c9d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
41 com.apple.HIToolbox 0x9152208e SendEventToEventTarget + 52
42 com.apple.HIToolbox 0x9158f444 ToolboxEventDispatcher + 86
43 com.apple.HIToolbox 0x9158bc9e RunApplicationEventLoop + 222
44 com.apple.finder 0x00023489 0x1000 + 140425
45 com.apple.finder 0x000f31e7 0x1000 + 991719
46 com.apple.finder 0x000094ba 0x1000 + 33978

Click here and follow the instructions.
(26907)

Unknown Group - Causes Finder Crash - How do I change group?

Many directories and files on my system after installing Leopard have an "Unknown" group and when I open a "Get Info" window on them and click the "Add" button the beachball appears and Finder crashes.
MacFixit stated "This problem appears to be due to a bad group setting. You can alleviate the issue by putting afflicted users back into the "Staff" group (GID 20) via the following Terminal command:
sudo dscl . append /Groups/staff GroupMembership username
(where "username" is replaced by the afflicted user's name)."
However, this did not solve my problem. Said files and directories still have "uknown" groups and Finder still crashes when I click the "Add" button in the Get Info window.
How to fix?

McToast wrote:
In Tiger, a group with the same name as your username would be created and the UID and GID would match. However, Leopard doesn't seem to be doing that anymore.
No, now it has reverted to the behaviour of 10.2 and before. All normal user accounts were made members of the "staff" group by default. admin users were also made members of the "admin" group, plus a couple of others. There are a lot more in Leopard. Trust me, you will have far fewer problems if you make your primary group 20. Your 'id' output should ideally look like
macbook:~ michaelc$ id
uid=501(michaelc) gid=20(staff) groups=20(staff),98(lpadmin),81(appserveradm),
103(com.apple.sharepoint.group.3),102(com.apple.sharepoint.group.2),
101(com.apple.sharepoint.group.1),104(com.apple.sharepoint.group.4),
79(_appserverusr),80(admin)
(I put some new lines in there to stop the excessively long line).
I don't know what those sharepoint groups are, either, in case you're wondering

Can't name new folders or rename existing folders in Finder

I can't name new folders or rename existing folders in Finder. I've never had this happen before. I tried both using the new folder icon and choosing "new folder" from the actions icon. The only unusual thing I'm doing now is working with Spaces enabled, but I can't imagine that this has anything to do with the problem. Selecting and hitting "return" doesn't allow me to either erase existing text or overwrite with new text. Any ideas?
Thanks.
Sue A.

Same here --
I just created a new folder and couldn't change its name. Finder would give me "more info" (permissions certainly not an issue) and allow me to delete (and then recreate) the folder, but not change its name.
Problem came from out of the blue, on a one-week-old system with all OS updates. Also found this old thread, which also suggests a Finder restart: http://discussions.apple.com/thread.jspa?messageID=8989639
So that'll probably do it, but what gives?
Not so impressed with 10.5.7 so far... first a complete system crash while doing no more than downloading updates (a few hours after booting up for the first time), then networking stopped working (see http://discussions.apple.com/thread.jspa?threadID=2003868), now this...

Finder crashes when clicking on Applications folder

VERY weird. Beginning a few days ago the finder on my Mac Pro crashes whenever I clicked on the Applications folder. It makes no difference what finder view I am using (icons, columns, etc.). Even if I click on the alias to the Applications folder in the sidebar, the finder crashes. I cannot view the contents of that folder by any method. The only way I can get to an item contained therein is to search for it using Spotlight.
Thinking that maybe my startup disk was hosed somehow, I ran Disk Utility (repaired permissions and verified the disk) and ran all tests within TechTool Deluxe. Both said the disk and filesystem were fine.
I tried copying the entire folder to another disk, but the copy aborts after the first few items (stops with Adobe Photoshop; the next item alphabetically is Aperture). In case Aperture was somehow a problem, I removed it (searched using Spotlight and then dragged it to the trash). No change in behavior.
I used Carbon Copy Cloner to replicate the entire drive to another, newly reformatted drive and made that drive the startup disk. No change in behavior.
It sure seems that the issue has to do with some kind of file corruption (that CCC dutifully replicated) rather than a faulty drive, but I have no idea where to look next for a solution (other than reformatting and reinstalling over 100 applications from scratch; ugh).
Does anyone have any idea what may be going on here? Until I can fix this, the Mac Pro is pretty much useless (luckily, I also have a MacBook Pro).

Hi - I too am having this issue.
When I click on any of the items in my sidebar (i.e. -desktop, documents, applications, etc...) this causes the finder to crash and restart.
I have tried trashing the com.apple.finder.plist and running disk utility but to no avail. I also found this other forum discussion (https://discussions.apple.com/thread/1336291?start=0&tstart=0) Where this was part of the post
petrock
Re: finder crashes when clicking desktop icon in sidebar - any help?
Feb 2, 2008 3:43 PM (in response to choegl)
choegl, that crash is the same place as andreas's but it got there in a different manor. In the manor I would expect it to. It is trying to retarget the window to your selection in the sidebar and setup List View according to the view options for that folder from that folder's .DS_Store. Its specifically trying to get the label for one of the columns in List View (i.e. Size or Name or Date Modified) but the value it gets from the .DS_Store is corrupt/bogus and causes the Finder to crash (specifically a component underneath the Finder call CoreFoundation via a call to CFStringGetLength). Here's how you solve your problem. In /Applications/Utilities/Terminal.app type: +cd <path to problem folder>+
+rm .DS_Store+
+killall Finder+ Pressing return after each line. You can get the path to the problem folder by drag/dropping the folder into the Terminal window. When the Finder comes back up, see if it still crashes when you click on that problem folder (i.e. your Desktop) in the sidebar. Repeat the steps above for any other folders that behave this way when you click on them in the sidebar. Hope that helps everyone...
btw, I wrote up a bug report on your behalf about this issue and sent it off to Apple (# 5721669)."
I tried this as well and nothing!
Anyone have any suggestions? I'm at a loss and am hating this issue! BTW, if I right click on any of the items in the sidebar, I can then click on open to get the folder to open. HASSLE! and if I forget (which is likely since I move too fast for my own good) then I crash the finder. Also, this happens on all the users on my mac.
Thanks!!!!
Matthew
MacBookPro 2,2 - OS X 10.6.8 - 2.16 GHz - 3 GB mem -

10.6.8 update + Time Machine = Finder crashing ;-(

Hi All,
After installing the 10.6.8 update to my Mac Pro, Time Machine will hang on the "Cleaning up" process. Time Machine cannot be exited from the Menu Bar. The finder may hang during this process, if "Force Quit", the finder cannot be relauched. The following error is presented :
The application Finder.app can't be opened. -10810.
One user on the Forums suggested backing up and re-formatting the drive. I'm not keen for this course of action. I have tried to copy the Time Machine dated folders onto an internal drive, but due to either a. the number of files (?) or b. The size of the backups this also fails.
Please advise if there is a fix for time machine / finder that does not involve wiping the External Drive.
Mac : MacPro 8-core/8GB/1TB/sd
Sys : 10.6.8.
Drives being backed up:
System : ~150GB
Data : ~ 300GB
Archive (online) : ~100GB
TM External Drive : Western Digital MyBook 1TB
Interface : FW800
Thanks in Advance.
Matt.

Hi Linc,
Thanks for the thought.
Downloaded the 10.6.8 update ( @ > 1GB !!) and re-run. No restart required. No change to functionality of the drive. Going to go with the Re-Format option. When Disk Utils is run - no problems are reported, yet accessing the drive not even with Time Machine switched OFF, can result in the Finder crashing (SWOD), force quit, then unable to restart Finder with the -10810 error.
So it would appear that this is not related to Time Machine but more :
External FW 800 drive vs. MacOS 10.6.8.
Keep you posted.
Matt.

Finder crash when opening any Folder

I am a very experienced mac user and this one has me stumped. Im posting here to see if anyone else has this problem.
Finder crashes when opening a folder on the desktop
Finder crashes when using any option from the Go menu (or key combo) except Airdrop.
Once Finder window is open on Airdrop any navigation to home folder or any other folder using side bar causes Finder to crash.
Using Go To Folder causes crash, even on hidden folder like /var
Finder is OK when opening files on desktop
All other apps can browse file system and open/save OK
Google Drive is not present on system (this used to be an issue a long time a go that caused similar symptoms in other threads)
Drop Box is installed. But issue occurs even when dropbox is not running
Using spotlight to open applications still works normally.
Clicking the Finder icon in the Dock results in a non-functional blank window entitled "Window", all tool buttons are disabled.
Repeatedly opening the same folder over and over results in the message "The last time you open Finder, it unexpectedly quite while reopening windows. Do you want to try to reopen its windows again? If you choose not to reopen windows, you may have to open and position the windows yourself" Two options "Don't Reopen" and "Reopen". Both buttons have no effect except to dismiss the dialog.
Steps Taken to fix:
Booted into recovery mode and performed repair disk and Permissions - Finder Still Crashes
Removed finder preference files using terminal
~/Library/Preferences/com.apple.finder.plist
~/Library/Preferences/com.apple.sidebarlists.plist
Recent changes to system:
iTunes 11.4 Installed with normal Software Update.
Possible Cause of Problem
Found app in iTunes that has File Sharing enabled and has a shared folder. Curious as to what was in the folder i dragged it to my desktop and double clicked. Im not sure if iTunes would have had enough time to copy the contents of the folder before i tried to open the folder. Finder crashed. This was the first time it happened.
iPhone app in iTunes that I picked in was "Ubersense".

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
Don't be put off merely by the seeming complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can read it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of the script have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
5. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
6. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts SerialATA 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports ' com.clark.\* \*dropbox \*GoogleDr\* \*k.AutoCAD\* \*k.Maya\* vidinst\* ' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 "` route -n get default|awk '/e:/{print $2}' `" 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB com.apple.AirPortBaseStationAgent 464843899 51 5120 files );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n-\t%s\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;/de: S|[nst]:/p;' ' {sub(/^ +/,"")};/er:/;/y:/&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Genesy|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { print "'${p[41]}'";if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$|'${p[41]}'/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/^root$/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1100) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/{next};/(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { print "'${p[41]}'.plist\t'${p[42]}'";if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|kMDItem'${p[35]}'=");sub("^...."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[43]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/{next};/%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|BKAg|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";p="uniq -c|sed -E '"'s/ +\$[0-9]+\$\$.+\$/\\\2 x\\\1/;s/x1$//'"'";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]$1|p;b=b$1;} END { close(p) if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text$|(Bo|PO).+ sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' s/^ +N.+ =//p;' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' ' /l: /{ /DVD/d;s/.+: //;b0'$'\n'' };/s: /{ /V/d;s/^ */- /;H;};$b0'$'\n'' d;:0'$'\n'' x;/APPLE [^:]+$/d;p;' ' /^find: /d;p;' "`S0 44 45`" );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' '" L*/P*/*loginit*' 'L*/Ca*/com.ap*.Saf*/E*/* -d 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;|sort|uniq' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'bad |Beac|caug|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:| VALI|xpma' -o -k Sender fseventsd -k Message Req 'SL' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Co{mpon,reM},Ex,Inter,iTu*/*P,Keyb,Mail/B,Pr*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -path \\*s/Resources -prune -o -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t /S*/L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' '+c0 -i4TCP:0-1023' com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' "+c0 -l|awk '{print(\$1,\$3)}'|sort|uniq -c|sort -n|tail -1|awk '{print(\$2,\$3,\$1)}'" );N1=${#c2[@]};for j in {0..9};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching SATA Descriptors );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 0 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;D20 0 $((N1+1)) 2;D10 0 $N1 1;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;D13 0 $((N1+9)) 59 50;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 35 49 61 51;D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D13 24 24 32 31;D13 25 37 32 33;A2 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D13 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D13 14 2 48 43;D13 4 5 32 1;D13 4 3 60 5;D12 26 48 49 49;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D22 4 4 50 0;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
8. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
11. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report what happened. No harm will be done.
12. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "You are not authorized to post." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Finder crashes and restarts when Adobe PDF documents are accessed.

Recently I've been having problems with my Finder crashing (window closes and the dot under the Finder icon in the Dock goes out) and restarting (dot under the icon in the Dock comes back on). The problem occurs when I select an Adobe PDF document in the Finder. I use column view. If I click once on a document to see the Preview information in the next column, or if I double click to open the document, the crash and restart occurs. However, it doesn't happen for all Adobe PDF documents. If the icon next to the document name in the Finder shows the first page of the document, the problem does no occur. But if the document icon remains the Adobe logo, the problem occurs.
I'm running Os X 10.5.5 on one of the early iMacs. Other than regular Apple updates, the only software change I've made recently is to install Adobe Flash Player.

Here's an update.
The problem seems to be confined to the Finder when Column view is selected. When List or Icon view is selected there is no crash and restart. When Cover Flow is selected the Finder crashes and restarts, but the pattern seems a bit odd. It crashes when some folders or subfolders are selected, but not others.
In Column view the problem occurs for some Adobe PDF documents where the document icon is the first page. It occurs for all PDF documents where the icon is the Adobe logo.

Finder Crashing after update

Hey Guys I have an old Macbook (2009) runing 10.6.8 that I recently ran some software updates on it and now everytime I try to open the utilities folder finder locks up and then closes and restart.
The mac is bogged down, and adding more ram doesnt make any difference. I've tried to repair the permissons via disk utility but still no luck, Created a second user (to make sure its not the profile) not sure what to do next? Any ideas?

Finder crashes are often caused by "Google Drive." If it's installed, I suggest you first check for an update. If that doesn't solve the problem, remove it according to the developer's instructions. You may need to start the computer in safe mode to do so. Back up all data before making any changes.
If you use Google Drive and don't want to remove it, then try deselecting the option in its preferences to "show status icons." According to reports, that may be enough to stop the crashing.
Similar cloud-data clients such as "Dolly Drive," "iDrive," "Open Drive," "Transporter Desktop," and others can cause the same problem.

Finder Crashes All The Time - Mountain Lion.

Helo there,
My iMac used to work just fine, but now after a year I got it, Finder crashes all the time. It doesn't show my folders, only some of them. I have to search to see them. When I open Finder, and try to work with it, I will get the loading colloured cirkel. Also Finder's sidebar doesn't show my favorites, airdrop or all my files. I can only see shared computers and extended drives and usb's. I've got two extended harddrives connected to my Mac, both of 1TB. One of them is my TimeMachine and the other is my old drive with movies. When I open the TimeMachine drive, I works just fine but when I open my older drive it will load very long and then show nothing. If I want to upload a picture on facebook or something like that, and I get the window to choose the file, it will lagg, stuck and not work, cause I can't see anything. I have to search it then with spotlight, and then select it. When Finder chrases and stuck with the spinning wheel, I restart Finder with second mouse option. Then I will have to wait very long until it opens again. The stuff on the desktop dissapears and I can't draw a selection area anymore. Also other programs crashing a lot more often, like disk utility and activity monitor. I thought it was immposible to work with a computer that crashes all the time. So what I did was:
Checking my harddisk with disk utility, and recover the things
Still stuck with the problem
Then
Make a TimeMachine backup.
Reboot the iMac holding the option key
Erase harddisk
Reinstall Moutain Lion
Reinstall backup
Repairing disk with disk utilities again
After this, I got the same issue and it drives me crazy. I've been to two local Apple resellers and told them my problem. They told me that it probably was a hardware issue. I have no idea my self so I ask you guys if you can help me out with this.
By the way:
one time when I restarted Finder, it wouldn't open and I got error code 600.
Last software that I installed was Paragon, I thought that it was causing the problem, so I deleted but it dind't helped. Now I got Paragon again.
Is this a software or a hardware problem and how should I fix this?
Thanks.

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. For instructions, launch the System Preferences application, select Help from the menu bar, and enter “Set up guest users” (without the quotes) in the search box. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
*Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
Test while in safe mode. Same problem?
After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

Permissions on folders damaged - Finder crashes on changing

Similar Messages

Maybe you are looking for