JRegistry / News: Recent posts

The documentation for this library can be found online at https://jregistry.sourceforge.io/docs/.

Changes in this release include:
--Fixed RegistryKey view64BitRegistry method not properly setting the KEY_WOW64_64KEY and KEY_WOW64_32KEY flags on Windows 10.

Changes in this release include:
--Fixed RegistryExporter IS_2000 being incorrectly reported as false on Windows 10.

Changes in this release include:
--Fixed RegistryQuota.compareTo method always returns 0.
--Fixed various bugs using the FindBugs tool.
--Changed the RegistryKey.serialVersionUID.
--Corrected various JavaDoc errors.

An update to fix a small error introduced in the new version when dealing with remote registry keys.

A new version of JRegistry is released. This release brings some new methods to assist with bulk operations such as RegistryKey.getValues(String...) to get a list of only the values that were specified.

Other additions include Iterators for both RegistryKey types and RegistryValue types.

The most notable addition is that Remote Registrys are now supported! That means that you can now connect to a registry on a different computer in your network provided that you have the necessary privileges to do so.

Changes in this release include:
--Using variable arguments in the RegistryValue, RegBinaryValue, and RegMultiStringValue classes.
--Allowing the use of the java.library.path system property to specify the location
of the JRegistry binary which should be loaded.

Here is a bug fix release. It fixes bugs that were found through FindBugs. Also added a new method for RegistryKey, restoreHive(File, boolean). Before the restore operation would try to force the hive to be restore even if open handles existed. Now you have the option to specify whether to have the system force the operation or not.

Also one last problem with serialization is fixed. Added a serialVersionUID value so that from this release onwards, objects that were serialized with version 1.7.5 would be read by and new release.

I have decided to distribute JRegistry under the LGPL (GNU Lesser General Public License) instead of the GPL (GNU General Public License).

Corrects possible synchronization problems and thread termination problems for RegistryWatcher.

Included a new api which allows for REG_EXPAND_SZ type values to be automatically expanded when calling RegistryKey.getValue(String), RegistryKey.getValues(), or when refreshing the data of a REG_EXPAND_SZ value.

The name is RegistryKey.autoExpandEnvironmentVariables(boolean).

You can also test to see if REG_EXPAND_SZ is automatically expanded by calling RegistryKey.isAutoExpandEnvironmentVariables() which returns a boolean.... read more

This release applies a fix for the Windows DLL Load Hijack vulnerability. Just make sure the DLL is in the same directory as the JAR library file.

Changed the version information for the dll files.

Fixed a bug with expandEnvironmentVariables always returning null. Introduced a new internal mechanism to make sure the right dll file is used with its corresponding library.

Added other various maintenance fixes.

This update includes smaller binary files for both 32-bit and 64-bit architectures.

Nothing is different about the files other than their sizes.

This update fixes a sorting bug between registry keys from different hives. (Ex: one from HKEY_CURRENT_USER and the second from HKEY_LOCAL_MACHINE)

Made SystemTime implement the Comparable interface. Added a new RegistryNotificationDispatchThread. This allows all events to be delivered from a single thread rather than multiple ones. No changes to any code should be necessary.

Fixed the reading of REG_QWORD type values. The problem was that the number was constructed with some bytes in the wrong order.

Adds the ability to search using a byte array. This allows for searching through all value types in the registry, not just strings or integers.

Also corrected some documentation regarding the index that is returned from the search functions.

Fixed a NullPointerException in RegistryExporter.

Fixed handle opening problem for 64-bit registry.

Fixed a small problem with getLastError() returning wrong error codes.

There was a small mistake in the documentation. No code changes were made between this update and version 1.6.0.

Also this new version breaks any existing serialization of RegistryKey objects because of the support for the 64-bit JRE.

This release brings support for 64-bit JREs with a new 64-bit DLL. Also there is are new method, view64BitRegistry(boolean) which will allow you to view keys under the 64-bit or 32-bit registry regardless of whether you have a 32-bit or 64-bit JRE.

Added two new methods to RegistryKey: getSubKey(String) and lastModified().

getSubKey(String) will return the subkey of the calling registry key if that subkey exists.

lastModified() returns a long, much like how File.lastModified() returns a long