Windows 10: Cannot import .reg. Error opening the file.

...There may be a disk or file system error.

Happens when double-clicking reg-file on the NAS-share, which is mapped as a network drive.
User is a user with admin rights (membership of Administrators group), and it is the first and only user that was created while W10 was installed.

So what I tried:
Run regedit as Admin, importing, no-go.
Placing reg-file on desktop and executing, OK.
Accessing via UNC, OK.
Log in as user Administrator, I can execute the reg-file from the NAS too.

I read something about taking ownership, so I tried it on that specific key, but still no go from the user-acct.

Though I don't quite understand, why if the key is owned by Group Administrators, I, as a part of that group, cannot exec a reg-file, especially only when a drive is mapped.
The various variables here just don't "compute" for me...

(if it helps, I cannot copy the .reg file from the NAS to the C-Drive directly, but have to copy to desktop first and then onto C:, with the prompt for admin permission.)

Though this WAS working as I upgraded my machine from Win7 -> Win10 previously, and was working on upgraded Win10 too. This only started happening after new install.

Any ideas what's going on here?

:)

 

Windows 10 regedit cannot import a reg file

I save a reg file in a directory with no spaces. I want to import back into the Windows 10 registry but receive an error message:

Cannot import <filename>.reg: Error accessing the registry.

I am running as Administrator and have full control.

What's wrong?

/steveA

 

Windows 10 regedit cannot import a reg file

I also have this problem in Windows10 and full admin rights. A .reg file intended to solve the Night Light problem was imported as successfully, however

data of the registry has not changed!

Who can help??

Regards, Albert

I never received a response and assumed that nobody had written so I never got back on to look. I never solved the problem and moved on. Not a critical item so didn't lose any sleep over it but was annoying as I've done this many times w/out issue with prior
Windows OS's. In answer to the one guy who did write back, I had a very short reg-hack with an extension of "reg" and tested in the same directory as my executable on the local hard drive "C". The reg-hack simply defined the default window dimensions of Notepad
which I was using to shell out to a report log data that end-users needed to verify an app I developed and didn't want to re-invent the wheel so I used Notepad. I also set some basic print-defaults so that it printed with a basic Windows font and font-size.
On these same machines I can manually browse to the Notepad keys in Regedit and manually set the parameters logged in as them but wanted to make sure it was always the same in case they made changes tot eh Notepad defaults.

Anyway, that's it in a nut shell. Thanks for the "blast-from-the-past Albert... I totally forgot this was still out there! ;-)