Windows 10: BSOD w/ 'admppm.sys' problem: Changing reg '3 > 4' : What does it ACTUALLY do? > REG...

Impact on battery session length? I used this "fix" but I'm wondering about impact on battery? When using only battery, will setting REGVALUE [Start: '4' ] in Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm deteriorate my battery session-length? REGKEY: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppmBSOD w/ identified WhoCrashed 'admppm.sys' problem: Changing regkey 'Start '3 > 4' : What does it ACTUALLY do? >

:)

 

Change the default action for .reg files

Sounds like a reasonable thing to do. Even though it warns you twice before it merges the changes, it can't hurt to set the default to be Notepad instead.

One way to accomplish this is shown below, but in testing I discovered that this takes away the merge option from the context menu. This means that if you want to actually import a reg file after doing this, you would have to open Registry Editor and choose
File > Import to do it.

1) Settings > Apps > Default Apps

2) Click Choose defaults by file type

3) Scroll down to the .reg entry and click it to change the default to Notepad

 

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

 

Windows 10 regedit cannot import a reg file

This is an old question but see that the original poster never replied to your question. I have the same problem.

Windows 10, 64 bit, reg file is a ".reg" extension. The reg file was an export from the notepad registry item and am trying to force settings on my end users with the reg-hack when they login. I get the same error as the gentleman above and am not sure how
to solve it. I have done reg hacks for many years with Win98-Win7 without any issues.

I have also opened the reg hack up with notepad and re-saved so the file isn't corrupted. I am also admin for our entire ms network which I thought might be the problem. I also added a command line switch "/reg:64" which one poster suggested would solve
it but while the error goes away and it appears to run, nothing in the registry actually changes.

Thanks in advance if you're still listening (I hope)!

Dan M