Jump to content
You must now use your email address to sign in [click for more info] ×

Photo 2.2.1.2075 VERY slow when opening explorer


Recommended Posts

Howzit!

Photo and Publisher take a long time to open the browser and change folders. 'Save As' also also takes a long time.  Sometimes I get a white screen. It eventually recovers but it takes a long time. Everything else seems to be fine. I have reset all settings to default and disabled hardware acceleration. Win10 on Dell XPS 13 9360

Please help.

Regards, 

Philip

Link to comment
Share on other sites

  • Staff

Hi @Philip58,

Welcome to the Affinity Forums :)

As far as I understand it, the Affinity app simply use Windows Explorer API to access your system folders, therefore the behaviour you're describing may not be caused by the Affinity apps themselves.

Are you able to provide a screen recording showing this issue for me, as it isn't something we've heard being reported previously?

If you're unsure how to take a screen recording, please check out our FAQ linked below - 

Are you opening/saving to an External Drive or Network location through Explorer? Do you see the same delays when opening/saving a file from your Desktop, for example?

Many thanks in advance!

Link to comment
Share on other sites

Hi, @Dan C

Thank you for your prompt response.  Much appreciated.

I am new to Affinity. Just bought it.

I have used ShareX to create the screen recording because the MS Game-thingy that you recommended wouldn't let me record Windows File Explorer.  I hope that's ok. 

The first few seconds of my screen recording show you how fast my Windows File Explorer is by itself.  The second part of the screen recording shows you how slow Affinity is in accessing the same folders.

All folders and files are local. I even paused OneDrive.

I really hope you can help.

Regards,

Philip58
Amanzimtoti, South Africa

Edited by Philip58
Link to comment
Share on other sites

  • Staff

Thanks for providing that for me - this isn't being reported by other users so may be specific to your machine.

From your recording, I note the following:

  • Within Explorer directly, you are navigating through OneDrive > Personal > Documents, however within Affinitys Explorer window you are navigating through This PC > Documents - does the behaviour change in Affinity when navigating the OneDrive location instead?
     
  • The Explorer window within Affinity has the Extension Filter set to 'PNG' currently - if you change this to 'All Documents', does this change the behaviour?
    image.png

Can you also please provide a screenshot of this Extension Filter list, when opening Explorer through Affinity? It should look similar to the below:
image.png

Many thanks in once again!

Link to comment
Share on other sites

Hi, 

Thank you for your time.

Navigation:

  • I altered the navigation to either include or exclude OneDrive folders: no change. 
  • I unmapped (disconnected) unused drives: no change.
  • I selected a folder that is not monitored by OneDrive: no change.

Filter list:

  • Changed the filter to 'All Documents': no change.

Image of filter list attached, as requested.

Any suggestions will be gratefully received.

Regards,
Philip

F4Z7iYst2O.png.fbbda831a87f13d4819ab386b4a7a26b.png

Link to comment
Share on other sites

  • Staff

Thanks for providing that for me Philip - everything seems to be correct here so I'm unsure why you are seeing this behaviour currently.

Therefore I'd like to suggest resetting the Affinity app back to default settings, to see if this resolves things for you. Please see the below link for more information on how to reset the app:

Please do let me know if this helps!

Link to comment
Share on other sites

Hi,

I have done a reset as indicated (selected all items in both panes) but there is no change. I also Googled 'slow file explorer' and made a few minor changes which I thought might help, e.g. removing an unused network drive from QuickAccess, but there is no change.

Affinity apps are the only apps on my laptop that have this problem. 

Here is something that might help you sleuth this problem:
Opening the file explorer in Affinity for the first time, as in 'File | Open', is fast.  Selecting another folder is slow.  Returning to the first folder (which opened fast the first time) is slow.  That makes no sense.

Note, too, that returning to the Affinity app after selecting (or not selecting) a file is also slow.

I do not know what else to do. I hope you can still help.

Regards,

Philip

Edited by Philip58
Link to comment
Share on other sites

Hi, 

In addition to the above, a workaround seems to be to right click on a folder, then select 'Open in New Window'.  Two downsides: first, I have lots of nested subfolders which leaves a lot of explorer windows open, and two, the file selected takes a LONG time to open. Task Manager shows a LOT of CPU usage during file electing and opening.

Please help.

Regards,
Philip

Link to comment
Share on other sites

  • Staff

Thanks for trying that Philip & my apologies for the delayed response here, as our team have been discussing further suggestions for you to try.

Can you please try:

  • Run as Admin - right-click the Affinity icon and select this option in the menu. 
  • Update Windows  - please check that Windows is fully updated, as it looks like there was a related issue that was fixed by Microsoft a while ago.
  • Checking any broken paths aren't present on your desktop? As this has caused similar issues in other apps, as reported here:
    https://stackoverflow.com/questions/70739230/navigating-the-file-system-with-netbeans-is-very-slow
  • Disable any active AntiVirus apps

If the above does not change the behaviour experienced, I'd suggest creating a new user account on your PC, then install the Affinity app for this new user. Does the same issue occur in the new user account please?

Many thanks for your continued understanding and patience here :)

Link to comment
Share on other sites

Hi, Dan,

Thank you for your reply.  I don't mind how long this takes to fix.

1. Running as Admin - no change.

2. Updated Windows - no change.

3. Searched for broken links (all users) - no change.

4. Disabled MS Defender anti-virus - no change.

5. Created new user (local login only) - problem does not exist on new user's Windows file explorer inside Affinity Publisher 2.3 - it works perfectly.

I can do a temporary work-around by switching users and sharing files but it's far from ideal. 

I welcome more suggestions. 

Regards,

Philip

Link to comment
Share on other sites

  • Staff

No problem at all, many thanks for trying these for me!

6 hours ago, Philip58 said:

Created new user (local login only) - problem does not exist on new user's Windows file explorer inside Affinity Publisher 2.3 - it works perfectly.

This indicates the issue is likely specific to your user account / local config and therefore I'd suggest performing standard Windows repair functions, to try and detect / fix this.

Please try running the DISM RestoreHealth command, followed by the SFC scannow command, as outlined here - 

https://support.microsoft.com/en-au/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

This should automatically detect and repair errors with your Windows install/local user account.

Does this change the behaviour of Explorer within Affinity for you please? :)

Link to comment
Share on other sites

Hi,  Dan,

 

Thank you for your suggestions.

1. DSIM  - no change.

2. SCANNOW - no change even though some errors were found.

 Please also note this behaviour: when I select a Publisher file inside Publisher's file explorer - even a small one of only 12 pages - it takes a long time to open the file inside the app.  When I select the same file from Windows file explorer (with the app closed) the file and the app open quickly. 

Any other suggestions?

 

Regards,

Philip

 

Link to comment
Share on other sites

Does this trigger also in File Explorer itself? There is an issue that can be sort of illusive at first. It'll say "working on it..." more often in the contents window when accessing directories and the green progress bar will run endlessly as it progresses. The problem gets worse overtime and you will have more problems reading/scanning folders and files. It's intermittent near the beginning, that's why it is more difficult to detect that there is even an issue. If it is indeed the same issue, it's caused by a corrupt cache via Quick Access history and can be fixed. It took a reboot or two for it to resolve my situation:

https://www.addictivetips.com/windows-tips/fix-file-explorer-working-on-it-message-windows-10/

Microsoft Windows 10 Home (Build 19045)
AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro
32GB DDR4 (3600Mhz); EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB
Monitor 1 4K @ 125% due to a bug
Monitor 2 4K @ 150%
Monitor 3 (as needed) 1080p @ 100%

WACOM Intuos4 Large; X-rite i1Display Pro; NIKON D5600 DSLR

Link to comment
Share on other sites

Hello, debraspicher,

 

Thank you for your suggestion.  There is no change to the behaviour of Affinity file explorer despite there having been some very old files in that folder. Note that I do not, and did not, have the slow green bar or the 'Working on it...' issue.

As mentioned, Windows file explorer and all other apps that open files all work 100% (apparently) on my laptop. It is only the Affinity file explorer that is very, very slow for the current user.

 

Regards,
Philip

Link to comment
Share on other sites

15 hours ago, Philip58 said:

Hello, debraspicher,

 

Thank you for your suggestion.  There is no change to the behaviour of Affinity file explorer despite there having been some very old files in that folder. Note that I do not, and did not, have the slow green bar or the 'Working on it...' issue.

As mentioned, Windows file explorer and all other apps that open files all work 100% (apparently) on my laptop. It is only the Affinity file explorer that is very, very slow for the current user.

 

Regards,
Philip

That's a shame. I had the issue when selecting files within program at first, then it spread. I don't seem to remember if it said "working on it" in the open file version or not, but the behavior was close enough to what you were experiencing I thought it was still worth mentioning.

Dan C is probably right the issue is the User account itself. The old school solution was to delete that user and and start anew... but I wonder if there is a better way now?

You could try peeking at Event Viewer> Windows Logs as a last resort and see if maybe it has information about the file explorer hangs. It may help further narrow down the cause there...

Here's other things to try: https://windowsreport.com/fix-file-explorer-problems-windows-10/

Microsoft Windows 10 Home (Build 19045)
AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro
32GB DDR4 (3600Mhz); EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB
Monitor 1 4K @ 125% due to a bug
Monitor 2 4K @ 150%
Monitor 3 (as needed) 1080p @ 100%

WACOM Intuos4 Large; X-rite i1Display Pro; NIKON D5600 DSLR

Link to comment
Share on other sites

Hi, debraspicher & Dan C,

Thank you for your suggestions. 

I launched Affinity Publisher and opened its file explorer. Then I launched Windows Event Viewer.  It logged three new critical events the details of which are below in chronological order. The Event ID and the Task Category are the same for all three critical events, namely, 1000 and (100), respectively.

I hope the three items below will be helpful in providing further ameliorative suggestions.  I feel there is light at the end of the tunnel.

Regards,
Philip
P. S.  Concerning your second suggestion, 'fix file explorer problems': Done much earlier in the sleuthing.  No change.


First Critical Error:

Faulting application name: Publisher.exe, version: 2.3.0.2165, time stamp: 0x65663ec4
Faulting module name: PSDPUIHandler.dll, version: 6.0.0.19, time stamp: 0x603e26cd
Exception code: 0xc0000005
Fault offset: 0x0000000000076a0c
Faulting process ID: 0x107c
Faulting application start time: 0x01da2b6f1367281a
Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt\App\Publisher.exe
Faulting module path: C:\Program Files\KONICA MINOLTA\PageScope Box Operator3\PSDPUIHandler.dll
Report ID: d60e9c3f-a842-4a70-aa70-4295e1905ad8
Faulting package full name: SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt
Faulting package-relative application ID: SerifEuropeLtd.AffinityPublisher2

NOTE: PageScope Box Operator is the app I use to access items scanned and stored on my printer. This does not function as a searchable 'drive' per se but the interface used to access the storage 'box' on the printer is similar to Windows Explorer.  In any event, Affinity should not be trying to 'look' there. 


Second Critical Error:

Faulting application name: Publisher.exe, version: 2.3.0.2165, time stamp: 0x65663ec4
Faulting module name: mfc120u.dll, version: 12.0.40664.0, time stamp: 0x59260d2a
Exception code: 0xc0000005
Fault offset: 0x0000000000288bfd
Faulting process ID: 0x107c
Faulting application start time: 0x01da2b6f1367281a
Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt\App\Publisher.exe
Faulting module path: C:\WINDOWS\SYSTEM32\mfc120u.dll
Report ID: f8ececd5-7f3b-43a9-b11b-99ea0637b748
Faulting package full name: SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt
Faulting package-relative application ID: SerifEuropeLtd.AffinityPublisher2

NOTE: This file is present in that folder and is dated 2017/05/24.  I do not know what it does, except that it is related to Visual C ++ which I do not use.


Third Critical Error:

Faulting application name: Publisher.exe, version: 2.3.0.2165, time stamp: 0x65663ec4
Faulting module name: PSDPUIHandler.dll, version: 6.0.0.19, time stamp: 0x603e26cd
Exception code: 0xc0000005
Fault offset: 0x0000000000076a0c
Faulting process ID: 0x107c
Faulting application start time: 0x01da2b6f1367281a
Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt\App\Publisher.exe
Faulting module path: C:\Program Files\KONICA MINOLTA\PageScope Box Operator3\PSDPUIHandler.dll
Report ID: 452ddbb8-fba3-4f8c-beba-a1f2f0042465
Faulting package full name: SerifEuropeLtd.AffinityPublisher2_2.3.0.2165_x64__3cqzy0nppv2rt
Faulting package-relative application ID: SerifEuropeLtd.AffinityPublisher2

There it is again.

 

Link to comment
Share on other sites

25 minutes ago, Philip58 said:

NOTE: PageScope Box Operator is the app I use to access items scanned and stored on my printer. This does not function as a searchable 'drive' per se but the interface used to access the storage 'box' on the printer is similar to Windows Explorer.  In any event, Affinity should not be trying to 'look' there. 

You might try your test again, but a bit differently.

First, close all the Affinity applications. Next, start File Explorer. Do those same errors in C:\Program Files\KONICA MINOLTA\PageScope Box Operator3\PSDPUIHandler.dll occur? If so, it's because Konica Minolta has hooked itself into File Explorer, perhaps so it can offer a right-click context menu option, or so it can add your printer's storage location to the File Explorer sidebar.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

Hi, Walt,

Thank you.

I did as you suggested. No new error was created in Event Viewer (that I could find). 

You are correct: PageScope does offer a right-click context menu option and it is in the File Explorer sidebar.  Is there any merit in uninstalling this app?  I suppose I could live without it - I'd rather have Affinity working properly. 

Is there anything else you can suggest?  

Regards,
Philip

Link to comment
Share on other sites

4 minutes ago, Philip58 said:

Is there any merit in uninstalling this app?  I suppose I could live without it - I'd rather have Affinity working properly. 

Is there anything else you can suggest?  

I have no other ideas. But it would probably be worth uninstalling the app, or at least (if it offers configuration options as some apps do) tell it not to insert itself into File Explorer, and see if that resolves the problem.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

9 minutes ago, Philip58 said:

Hi, Walt,

Thank you.

I did as you suggested. No new error was created in Event Viewer (that I could find). 

You are correct: PageScope does offer a right-click context menu option and it is in the File Explorer sidebar.  Is there any merit in uninstalling this app?  I suppose I could live without it - I'd rather have Affinity working properly. 

Is there anything else you can suggest?  

Regards,
Philip

If that is what EV is telling you is consistently causing your error, then it is absolutely worth wiping it from existence. (I would uninstall and then check with Konica if a new version was released that fully resolves the issue)

Microsoft Windows 10 Home (Build 19045)
AMD Ryzen 7 5800X @ 3.8Ghz (-30 all core +200mhz PBO); Mobo: Asus X470 Prime Pro
32GB DDR4 (3600Mhz); EVGA NVIDIA GeForce GTX 3080 X3C Ultra 12GB
Monitor 1 4K @ 125% due to a bug
Monitor 2 4K @ 150%
Monitor 3 (as needed) 1080p @ 100%

WACOM Intuos4 Large; X-rite i1Display Pro; NIKON D5600 DSLR

Link to comment
Share on other sites

Dear Dan C, debraspicher and walt.farrell,

 

Thank you!  

Sorted.  What a relief!

I am most grateful for your patience, kindness and expertise in solving this problem.  I have learned a lot as a result. 

 

Again, thank you so much.

 

 

Regards,
Philip
Amanzimtoti, South Africa

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.