Fixing macOS Ventura Permissions for Folder and Files Opening as SKIMPDF

Folders and files opening as SKIMPDF in macOS Ventura typically indicate a corrupted file association or permission conflict where the system incorrectly maps standard documents to the Skim PDF viewer. This behavior often stems from misconfigured LaunchServices databases or lingering quarantine attributes that force specific applications to handle generic file types. To resolve this issue, you must first correct the default application assignments for affected file types. If the problem persists due to underlying permission errors, resetting these associations through System Settings is necessary. For deeper issues involving file metadata, removing quarantine attributes may be required. This guide provides a comprehensive approach to restoring normal file opening behavior without resorting to outdated disk repair utilities.

Correcting Default Application Assignments

The most common cause of files opening with an unexpected application like Skim is a broken default app setting. macOS uses the LSHandler registry to determine which app should open specific Uniform Type Identifiers (UTIs). When this mapping becomes corrupted, any file type might trigger the wrong handler. You can manually reset these associations using the Finder interface, which updates the user-level preferences correctly.

• Select the Affected File: Locate a file that opens incorrectly in SkimPDF. Right-click (or Control-click) on the file icon.
• Open Info Panel: From the context menu, select Get Info. Alternatively, press Command + I.
• Change Open With: In the "Open with:" section, click the dropdown menu. Select the application you actually want to use (e.g., Preview, TextEdit, or your preferred PDF viewer).
• Apply to All: Click the Change All... button below the dropdown. Confirm the action in the dialog box. This updates the association for all files of that specific type.

Repeat this process for each file type exhibiting the issue (e.g., .pdf, .txt, .docx). If you are dealing with many files, this method ensures that the user-level defaults are corrected without affecting system-wide configurations unnecessarily.

Resetting the LaunchServices Database

If correcting individual file associations does not stop folders or files from opening in SkimPDF, the global LaunchServices database is likely corrupted. This database caches information about available applications and their capabilities. Corruption here can cause the system to suggest incorrect apps for various file types, including directories. Rebuilding this database forces macOS to rescan all installed applications and re-establish valid file associations. You can do this via Terminal.

1. Open Terminal: Navigate to /Applications/Utilities/ and launch Terminal.app.
2. Execute the Reset Command: Type the following command exactly and press Return:

   /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user

3. Wait for Completion: The command runs silently. It may take a few minutes depending on the number of applications installed. Do not interrupt it.
4. Restart Your Mac: After the command completes, restart your computer to ensure the new associations are loaded into memory.

This procedure is safe and non-destructive. It does not delete personal files or settings but rebuilds the index that tells Finder how to interact with applications. This is the modern equivalent of older "Repair Disk Permissions" tools, tailored specifically for APFS volumes in Ventura.

Removing Quarantine Attributes

Sometimes, files downloaded from the internet or transferred between systems carry a "quarantine" attribute. This metadata tag can interfere with how macOS handles the file, potentially causing it to open in a restricted or unexpected viewer if the original source was associated with Skim. While less common for local folders, this can affect recently imported documents. You can remove these attributes using the xattr command. Before proceeding, ensure you understand which files are affected to avoid unintended side effects.

1. Identify the Path: Note the full path to the problematic file or folder. You can drag the file from Finder into the Terminal window to auto-fill the path.
2. Remove Attributes: Use the -d flag to delete the specific quarantine attribute. Run the following command:

   xattr -d com.apple.quarantine /path/to/file

   Replace /path/to/file with the actual path. For a folder and its contents, add the -R flag for recursive removal:

   xattr -R -d com.apple.quarantine /path/to/folder

3. Verify Removal: Check if the attribute remains by running:

   xattr /path/to/file

   If no output appears, the attribute has been successfully removed.

Be cautious when using recursive commands on large directories. Always verify the path before executing xattr commands. If you are unsure about the impact, consult our guide on Unabling Remove Attributes Files Using xattr on Mac for more detailed explanations of attribute management.

Checking for Conflicting Extensions

In some cases, third-party applications install extensions that hook into the file opening process. If SkimPDF or a similar tool has registered a system-wide extension for handling documents, it might override default behaviors. Check your Login Items and Extension Manager to identify potential conflicts.

• Review Login Items: Go to System Settings > General > Login Items. Look for any PDF-related tools or document managers that are set to open at login.
• Disable Unnecessary Tools: If you find a document manager or PDF utility that is not essential, toggle it off or remove it from the list.
• Check Extensions: Navigate to System Settings > Privacy & Security > Extensions. Review any kernel extensions or automation scripts related to file handling. Disable any that seem suspicious or unnecessary.

Conflicts with other security or VPN software can also alter traffic or file routing. If you use specialized network tools, check MacOS Viscosity VPN blocks non-Apple app traffic to see if network filters are interfering with local file access protocols.

Frequently Asked Questions

Why did my folders start opening as PDFs?

This usually happens when the file type association for directories is mistakenly linked to a PDF viewer. macOS treats certain directory structures as data bundles, and if the default handler is corrupted, it may attempt to render them as documents. Rebuilding the LaunchServices database typically resolves this by resetting the system's understanding of folder icons and handlers.

Is it safe to run lsregister -kill?

Yes, running the lsregister command with the -kill and -r flags is completely safe. It only clears the cache of application registrations; it does not delete any files, applications, or user data. Your Mac will simply take slightly longer to load file previews the next time you open a folder while it rebuilds the cache.

How do I fix permissions for a single file without affecting others?

You can use the chmod command in Terminal to adjust permissions for a specific file. For example, chmod 755 filename.pdf sets read/write/execute for the owner and read/execute for others. However, if the issue is strictly about the app opening the file, changing the default app via Get Info is safer and more appropriate than modifying Unix permissions.

Can antivirus software cause files to open in the wrong app?

While rare, some antivirus suites install kernel extensions that intercept file operations. If you have recently installed security software, check its settings for any "file inspection" or "document preview" features. Disabling these features temporarily can help determine if the antivirus is causing the association conflict.

What if SkimPDF is not installed anymore but files still open with it?

If the application is uninstalled but the association remains, the system may try to launch a ghost entry. Running the lsregister reset command will detect that the application bundle is missing and remove the invalid association. After the reset, you can assign a new default app for those file types.