This seems to be a known bug (as found via the "view/report bugs" link of Win32::Registry). There also seems to be a patch available, as posted in that bug report. If you can report that patch as working, it might incite somebody to adopt the module just to apply that patch.

If you are in a bind to modify the Windows registry, maybe consider Win32API::Registry.