Fixing the ERROR_NOTIFICATION_GUID_ALREADY_DEFINED Issue

The error code ERROR_NOTIFICATION_GUID_ALREADY_DEFINED 309 (0x135) accompanied by the message “The specified file already has a notification GUID associated with it”arises when a service or application attempts to register a GUID (Globally Unique Identifier) for notifications or other processes, but that GUID is already in use.

This situation can occur in various scenarios, such as file system notifications, event subscriptions, or other Windows-related notifications. To resolve this issue, start by rebooting your computer to release any resource locks, and then consult the Windows Event Viewer logs for more insights into the error.

How can I resolve the ERROR_NOTIFICATION_GUID_ALREADY_DEFINED?

1. Understand the context & check for duplicated GUIDs

When dealing with an application or service that registers a GUID, ensure that you aren’t registering the same GUID multiple times, as it must remain unique within its scope.

It’s advisable to review the logic of the application to identify any flaws in its flow. If any issues are discovered, consider restarting the relevant services.

2. Verify notification settings

1. Press Windows + I to launch the Settings app.
2. Navigate to System, then click on Notifications.
   

   

3. Investigate if any apps or services are misbehaving in sending notifications, and determine if there’s a GUID-related issue.
   

   

3. Inspect for duplicate entries in the registry

1. Press Windows + R to bring up the Run dialog.
   

   

2. Type regedit and hit OK to open the Registry Editor.
3. Press Ctrl + F to search for GUIDs related to the error.
   

   

4. Look for any duplicate entries; if you find any, either remove or rename them.

4. Look for updates

1. Open the Settings app by pressing Windows + I.
2. Go to Windows Update and select the Check for updates button.
   

   

3. If updates are available, click on Download & install to acquire the latest updates.

5. Reset or reinstall the application

1. Open the Settings app with Windows + I.
2. Go to Apps, and then click Installed apps.
   

   

3. Locate the problematic app, click on the three-dot icon, and choose Advanced options from the menu.
   

   

4. In the next window, go to the Reset section and hit the Reset button. Note that this action will delete the app’s data, necessitating a login afterward.
   

   

If resetting doesn’t resolve the issue, follow these steps to reinstall the app:

1. Head back to Apps, then choose Installed apps again.
2. Click the three-dot icon beside the affected app, followed by Uninstall from the context menu.
   

   

3. Confirm by clicking Uninstall.
   

   

4. Visit the official website or the Microsoft Store to reinstall the app afterward.

6. Execute SFC & DISM scans

1. Press the Windows key, type cmd into the search box, then select Run as administrator.
   

   

2. To scan for and repair corrupted system files, copy and paste the following command and hit Enter : sfc /scannow
   

   

3. Once the scan finishes, for checking and restoring Windows images via Windows Update, type this command and press Enter : Dism /Online /Cleanup-Image /RestoreHealth
   

   

4. After the successful completion of the scans, restart your computer to apply the changes.

If you continue to experience the issue, it may be time to reach out for support from the application or service that is generating the error.

In summary, resolving the ERROR_NOTIFICATION_GUID_ALREADY_DEFINED BSoD error entails reviewing details such as logs and error codes, examining the GUID and notification settings related to the app, resetting or reinstalling the application, and performing system file and DISM scans for repairs.

If you have any feedback or questions regarding the BSoD error, please feel free to leave your comments below.