Photoshop: Wakes/spins up up all disks on startup - even drives it shouldn't need to access. (Win 7/Win 10)

  • 1
  • Problem
  • Updated 2 years ago
  • Not a Problem
  • (Edited)
Photoshop wakes up all disks on startup - even drives it doesn't need to access.
This causes Photoshop to hang while it waits for sleeping drives to spin up.

The Photoshop installation and scratch disk is located on other (SSD) drives. No applications are installed on the HDD that Photoshop insists on waking up. No files that I work on are stored there.

Why does Photoshop need to wake up all drives on startup? Other applications do not need/do this.

Confirmed in CS6 and CC, under Windows 7 and Windows 10. A quick Google search seems to indicate this affects Photoshop Elements as well.
Photo of Jonas Madsen Rogne

Jonas Madsen Rogne

  • 21 Posts
  • 2 Reply Likes

Posted 3 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Photoshop is asking the OS for the type of volume, the size of the volume, and the free space on the volume. And some OSes don't cache that information and want to spin up the drives. Photoshop is simply asking for information that should be immediately available, and is not intentionally spinning up drives, but the OS spins them up anyway.

Other applications that check the size of the drives have the same behavior.
Photo of Jonas Madsen Rogne

Jonas Madsen Rogne

  • 21 Posts
  • 2 Reply Likes
Why does Photoshop need to ask for this information about every single drive on the system when starting the program?

E.g. InDesign does not have this behaviour.

Shouldn't it be sufficient to just know this information about the drives it actually needs to use? Or perhaps there is some other method of asking for this information that doesn't cause Windows to spin up the drives?
Photo of Mike Bruce

Mike Bruce

  • 13 Posts
  • 13 Reply Likes
I agree that this behaviour is dumb, and I don't remember it being an issue before. Even if PS does ask the OS for that information, I don't see why PS had to code the app to hang until the OS gives the information. I have to wait 10 secs while drives spin up. I understand that OS should provide this quicker, but, clearly it doesn't. So why does PS hang in the meantime? To blame this on the OS, as Chris Cox is famous for, is a little bit naive wouldn't you say?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Photoshop doesn't cause the hang. Photoshop asks the OS for the information, the OS wakes up the drive and blocks the application until it has the information.
I only blame things on the OS that are actually being done by the OS.
Photo of Mike Bruce

Mike Bruce

  • 13 Posts
  • 13 Reply Likes
Thanks. Then perhaps PS could be configured not to ask for that information? I never experienced this problem with previous versions.
Photo of Mike Bruce

Mike Bruce

  • 13 Posts
  • 13 Reply Likes
There's some more feedback on this incredibly frustrating problem here: https://www.reddit.com/r/photoshop/comments/3r0tv9/photoshop_wakes_up_all_of_my_hard_drives/

I'd like to know at which version this problem emerged. Is it limited to CC 2015? It's annoying because I don't want photoshop to access any of my hard drives apart from my SSD C: drive. Each time those drives spins up is shortening their lifespan and increasing the chance of failure. It would therefore be helpful to have a setting that we could disable this intrusive, unwanted and unnecessary behaviour.

I realise that the adobe employees on this forum essentially have a career of deflecting blame from Adobe, so it would be nice if others who suffer from this problem could speak up, and hopefully we'll get them to listen. Thanks

ps - I'd also like to know why this issue was classified as 'not a problem' when it clearly is a problem.
(Edited)
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Photoshop has checked the status of drives in the system for over 20 years.  This is caused by a bug in your OS that is forcing the drives to spin up when the information asked for should already be cached by the OS.

And nobody is deflecting blame - we're just explaining the way things are.