Details: On deployed machines only, the Log folder & UIU data folder have been migrated from Program Files to ProgramData. UIU log files on deployed machines are now located under the ProgramData\UIU directory. Additionally, resources needed by each application are extracted/placed in the ProgramData\UIU\bin directory (temporarily). Program Files is no longer used for any resources or logs. NOTE: The UIU 5 Installation log files are also now located in ProgramData\UIU; other install files remain in Program Files.
Trial product expires ON the expiry date. Detail: On the date of expiration (as indicated on the UIU Trial documentation), the Trial product will cease to function in accordance with the UIU License Agreement.
Trial Product Conversion to Live product. Detail: Trial product of the UIU v5 may now be converted to Live product if UIU v5.4.2.0 was used to install the Trial product. When a Live product is purchased and a Live UIU License Key is obtained, the Trial product may be uninstalled without removing the associated repository and the UIU v5.4.2.0 may be re-installed using a the Live UIU License Key and may use the pre-existing repository, eliminating the need to re-establish a repository. Online Updates may then be performed to update the UIU Driver Database and future versions of the UIU v5.
Discovery Tool Improvements Detail: Discovery Tool is now executed when UIUPrep.exe is launched with the "-dt" switch and will produce logs in ProgramData\UIU\DiscoveryTool\DiscoveryTool.log. This procedure will further create a .uiudt file in the DiscoveryTool directory based on the Make/Model/Date of the machine run on. Online analysis requires Internet connectivity and a further switch: -analyze. For Example: uiuprep.exe -licensekey "<UIU License Key>" -dt (Scans, writes to the log, creates a .uiudt file.) uiuprep.exe -licensekey "<UIU License Key>" -dt -analyze (Scans, uploads for analysis, writes to the log (including analysis results), and creates a .uiudt file.)
Windows 10 ADK support updated. Detail: ADK support updated to utilize Windows ADK 10.1 (from 10); DISM version 10.1.10586.0 (from 10.0.26624.0).
Symptoms: Boot+ Feature fails to launch. Resolution: Code corrected to properly launch Boot+ Feature under various configurations. Additional, improved cancellation support has been included to allow the process to be cancelled while adding drivers (instead of not cancelling until the driver add process was complete.)
Symptoms: Custom was determining the parent directory to be valid, and then causing all files/folders to be copied as "custom" drivers. resulting in false-positives. Resolution: With respect to custom paths, if a provided path was not accessible, the parent directory is considered. Handling Custom Paths has been adjusted so that if multiple Custom paths are provided, each is considered to determine the "best" source; but if their path does not exist, a parent directory is no longer considered.
Symptoms: Trigger handling would fail due to an inability to access the offline registry. Drivers applicable to a particular pnpID would not be presented for enumeration. Resolution: Trigger handling modified to be able to access the offline registry properly.
Symptoms: NVMe hard disk (controller) drivers fail to install properly in Windows 7. Resolution: Added support for KB2990941, which adds NVMe hard disk (controller) support to Windows 7. This KB is included within UIUPrep and is extracted/installed automatically on Windows 7 platforms.
Symptoms: When attempting to install/update, the UIU 5 does not have SQL CE 4.0 support, causing the Installer/Updater to fail.. Resolution: The UIU5 Updater now includes SQL CE 4.0 resources and will attempt to extract and load the resources as necessary when launched. This successfully resolves the two following "RESOLVED Issues"
Symptoms: This is a known Microsoft issue. The Microsoft Windows Global Assembly Cache (GAC) is a registry that provides the operating system with the locations of libraries (dlls) and is accessed when a program requires a registered library to be loaded into memory. For undetermined reasons, when Microsoft SQL Server Compact 4.0 is uninstalled, an orphaned record remains in the GAC, pointing to a location that contains no libraries. The UIU 5 requires SQL CE to be present and during install, will copies files for use to a temp location. When the UIU 5 install attempts to extract the necessary SQL CE files and load them, Windows accesses the GAC and attempts to load SQL CE from the GAC-registered location. Therefore, if SQL CE had previously been present and was subsequently uninstalled, the SQL CE libraries will not be present in the GAC-registered location (as opposed to the UIU established location) and will fail to load, causing the UIU 5 Installation to hang during the construction of the repository. Resolution: At this time, the most efficient solution is to re-install Microsoft SQL Server Compact 4.0. The download may be obtained using this link.
Symptoms: This is a known Microsoft issue. The Microsoft Windows Global Assembly Cache (GAC) is a registry that provides the operating system with the locations of libraries (dlls) and is accessed when a program requires a registered library to be loaded into memory. For undetermined reasons, when Microsoft SQL Server Compact 4.0 is uninstalled, an orphaned record remains in the GAC, pointing to a location that contains no libraries. The UIU 5 requires SQL CE to be present and during Online Updates, and relies on files copied during the UIU 5 installation. When the UIU 5 Updater attempts to extract the necessary SQL CE files and load them, Windows accesses the GAC and attempts to load SQL CE from the GAC-registered location. Therefore, if SQL CE had previously been present and was subsequently uninstalled, the SQL CE libraries will not be present in the GAC-registered location (as opposed to the UIU established location) and will fail to load, causing the customer to receive the following (when attempting to update the UIU 5): “Error: "Failed to load driver udb". The UIU 5 Online Updates will fail. Resolution: At this time, the most efficient solution is to re-install Microsoft SQL Server Compact 4.0. The download may be obtained using this link.