Fix DOM RegDll.bat execution failure with UNC path error

draft · practice-management domregistrywindows

Generated by docuprocessor (prompt article/v3) · 2026-04-22 14:44

Source thread

thread_id: spaces/AAAA05BdS6s/threads/6eEUo02Ur7I · 16 msgs · first 2025-01-03 · participants: Tech ATech B

Tech A 2025-01-03 19:55

@all Guys, so how do we install DOM for Dr Boyd? Is there a manual?

Tech A 2025-01-03 19:55

oh, wait, i forgot that @Josue Nasini made one...

Tech B 2025-01-03 20:04

Let me know if you ran into any issues or something, I can check with you

Tech B 2025-01-03 20:04

I did some modifications to the article since we had new issues after I created it lol

Tech A 2025-01-03 20:05

i did. the registry you are referring to does not exist

Tech A 2025-01-03 20:05

this part

image/png image.png

The image shows documentation text describing a fix for the error message **"Unexpected error # from DOMSQL accessing object brsPrinterSet"** encountered when opening DOM. The resolution involves adding a registry value **DisableUNCCheck REG_DWORD set to 1 (Hex)** under the path **HKEY_CURRENT_USER\Software\Microsoft\Command Processor**. A note specifies that on **Windows 10 version 1803**, the setting may instead be located under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor**.

Tech A 2025-01-03 20:06

there is no Command Processor in registry

Tech B 2025-01-03 20:08

Have you tried both? Second one worked for me

image/png image.png

The image shows a technical support document describing the error message **"Unexpected error # from DOMSQL accessing object brsPrinterSet"** occurring when opening DOM. It instructs adding a registry value **DisableUNCCheck REG_DWORD set to 1 (Hex)** under the path **HKEY_CURRENT_USER\Software\Microsoft\Command Processor** (highlighted in a red box). A note indicates that on Windows 10 version 1803, the setting may instead be located under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor** (also highlighted in a red box).

Tech B 2025-01-03 20:08

U have to do that registry thing in case that you receive an error when you execute RegDll.bat

Tech B 2025-01-03 20:08

It closes quickly

Tech B 2025-01-03 20:09

It show you something at the first lines, something about UNC Path

Tech A 2025-01-03 20:11

I ran RegDDLs again but this time not as admin and it worked after

Tech A 2025-01-03 20:12

just need to add pause to that batch file so it does not close

Tech A 2025-01-03 20:12

let me do it

Tech A 2025-01-03 20:14

well, it makes sense now after I looked at the batch file. Since its uses current user registry, me running it as admin added it to the admin's account...

Tech A 2025-01-03 20:14

thanks, Josue

---
title: "Fix DOM RegDll.bat execution failure with UNC path error"
category: practice-management
tags: ["dom", "registry", "windows"]
source_thread_id: "spaces/AAAA05BdS6s/threads/6eEUo02Ur7I"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T14:44:49"
participants: ["Tech A", "Tech B"]
---

# Fix DOM RegDll.bat execution failure with UNC path error

## Problem
When installing DOM, the RegDll.bat file may close quickly without completing registration, displaying an error about UNC paths in the first lines. This prevents proper DOM installation and can result in the error "Unexpected error # from DOMSQL accessing object brsPrinterSet" when opening DOM.

## Resolution
1. Run RegDll.bat as a regular user (not as administrator), since the batch file modifies current user registry settings
2. If the UNC path error persists, add the registry value `DisableUNCCheck` as REG_DWORD set to 1 (Hex) under one of these paths:
   - First try: `HKEY_CURRENT_USER\Software\Microsoft\Command Processor`
   - If the above path doesn't exist or doesn't work (particularly on Windows 10 version 1803): `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor`
3. To troubleshoot batch file execution, add `pause` to the end of the RegDll.bat file to prevent it from closing immediately

The key insight is that running RegDll.bat as administrator causes it to modify the administrator account's registry instead of the current user's registry, which is why running it as a regular user resolves the issue.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/6eEUo02Ur7I`
- Attachments:
  - ![image.png](../attachments/6eEUo02Ur7I.QdtXt0IeA7s/image.png) — The image shows documentation text describing a fix for the error message **"Unexpected error # from DOMSQL accessing object brsPrinterSet"** encountered when opening DOM. The resolution involves adding a registry value **DisableUNCCheck REG_DWORD set to 1 (Hex)** under the path **HKEY_CURRENT_USER\Software\Microsoft\Command Processor**. A note specifies that on **Windows 10 version 1803**, the setting may instead be located under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor**.
  - ![image.png](../attachments/6eEUo02Ur7I.qcAbZTfDYm0/image.png) — The image shows a technical support document describing the error message **"Unexpected error # from DOMSQL accessing object brsPrinterSet"** occurring when opening DOM. It instructs adding a registry value **DisableUNCCheck REG_DWORD set to 1 (Hex)** under the path **HKEY_CURRENT_USER\Software\Microsoft\Command Processor** (highlighted in a red box). A note indicates that on Windows 10 version 1803, the setting may instead be located under **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor** (also highlighted in a red box).

Generated article

draft