Skip to main content
S
sheldong26810370
Known Participant
December 31, 2024
Answered

Event ID 1000 when closing

  • December 31, 2024
  • 1 reply
  • 379 views

Photoshop 26.2 on a PC with WIN10 22H2 with latest update.  When I close Phtotshop with a image previously opened, it produces an Event 1000 by NTDLL.DLL.  Doeesn't matter if the image is closed on not when PS is closed.  Doesn't matter if the image is presented to PS via LrC or directly.  If I hadn't been looking in the Event Viewer, I would never relealized this has been occuring.  Bottom line this issue doesn't effect PS while it's running but I still woud like to find the root cause.

Correct answer Sameer K

Hey, @sheldong26810370. Welcome to the Photoshop Community. I'll help you figure this out. 

While the existence of the error is not uncommon, it could be unrelated to just Photoshop. This error can be related to:

  • Corrupted Microsoft Visual C++ directories. 
  • Corrupted .NET Framework components.
  • Graphic Drivers.
  • Corruption of the ntdll.dll, which is a System DLL. 
  • Other OS-level issues.

Most of the time, the error is rectified on the OS rather than in Photoshop. There are past conversations I found in MS Community: https://adobe.ly/3BNA5HV

 

Let me know if it helps.
Thanks!

Sameer K

(Type '@' and type my name to mention me when you reply)

1 reply

Sameer K
Community Manager
Sameer KCommunity ManagerCorrect answer
Community Manager
January 1, 2025

Hey, @sheldong26810370. Welcome to the Photoshop Community. I'll help you figure this out. 

While the existence of the error is not uncommon, it could be unrelated to just Photoshop. This error can be related to:

  • Corrupted Microsoft Visual C++ directories. 
  • Corrupted .NET Framework components.
  • Graphic Drivers.
  • Corruption of the ntdll.dll, which is a System DLL. 
  • Other OS-level issues.

Most of the time, the error is rectified on the OS rather than in Photoshop. There are past conversations I found in MS Community: https://adobe.ly/3BNA5HV

 

Let me know if it helps.
Thanks!

Sameer K

(Type '@' and type my name to mention me when you reply)

    S
    sheldong26810370Author
    Known Participant
    January 1, 2025

    Ran SFC per recomendation on the link and it seemed to fix the issue -

    Thanks

      S
      sheldong26810370Author
      Known Participant
      January 1, 2025

      Common practice is to run DISM /RestoreHealth prior to running SFC. May want to include DISM in your routine maintenance.  dism /online /cleanup-image /checkhealth or  dism /online /cleanup-image /scanhealth


      I did run DISM /RestoreHealth prior to running SFC.

      Thanks

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices