-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have 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
Preview functionality only works on desktop, not in other folders #1489
Comments
In video, you installed the FolderViewer plugin. |
Unfortunately, this issue existed before I installed any plugins. I thought the lack of plugins might be the problem, so I downloaded and installed the folder plugin, but the issue persisted. While editing this message, I tried uninstalling it, but the problem still remains. The preview feature only works on the desktop and not in other folders, regardless of whether the FolderViewer plugin is installed or not. |
I can't reproduce the problem you describe in Windows 11, I haven’t used Windows 10 for many years. |
Is there a way to export the log file so I can possibly figure out why is the problem occurred? Another Win10 PC of mine works fine with this tool, so it shouldn't be an issue of Win10. |
Look for |
Description
After installing QuickLook on Windows, I've noticed that the preview functionality is only working for files on the desktop. When trying to preview files in other folders, the feature does not work at all.
Steps to Reproduce
Expected Behavior
The preview functionality should work in all folders, not just on the desktop.
Actual Behavior
The preview only works for files on the desktop. In all other folders, pressing the spacebar does not trigger a preview.
Environment
OS: Windows [your Windows version, e.g., 10 or 11]
QuickLook version: MSI 3.7.3
Additional Information
This behavior is consistent across different file types
The issue persists after restarting the computer and the QuickLook application
Screenshots and Exception Log
Couldn't find the Log in the file's location, but attached a video showing the issue.
https://github.com/user-attachments/assets/6c6915c4-d015-43a8-b0ab-66f079b85ac2
The text was updated successfully, but these errors were encountered: