866-754-3592

Release Notes

rss

2.2.0.0 - UIU Plug-ins 2.0 with SCCM - Upgrade Release Bookmark



February 20, 2018
Includes UIUprep version 5.6.0.0


Please refer to the UIU Plug-ins 2.0 - SCCM User Guides for detailed implementation and usage instructions.


This release of the UIU Plug-ins 2.0 includes general code review and clean-up.

The MDT and SCCM Plug-ins now accurately record the UIU License Key in their Task Sequence Properties (XML files). This change is cosmetic as the correct UIU License Key was already applied to the UIU task element.

The UIU Plug-ins 2.0 for SCCM version 2.1.0.0 also includes support for 1E Nomad/Active Efficiency. Please contact UIU Support for details.


Issue: UIU-created Packages Uneditable

Symptoms:
An unforeseen character limitation in the Comment field of SCCM's package properties was surpassed, rendering the UIU-created packages uneditable unless the comment was shortened.

Resolution:
As of the UIU Plug-ins 2.0 (v2.1.0.0), upon creation of SCCM packages by the UIU Plug-ins 2.0, the comment included was reduced to a quantity less than that of the undocumented character limitation.



REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

Features - SCCM (as of version 2.0.0.0)

  • More robust UIU Repository management with automated checks for integrity

  • Enhanced delivery of the UIU Driver Database

  • Improved integration with SCCM native controls

  • New hybrid methodology for Content Delivery, reducing bandwidth and local storage needs while decreasing driver acquisition times during OS Deployment Task Sequence

  • New and improved user interface

  • Ability to create and manage the UIU Repository from any administrator PC

  • One-click opt-in access to unreleased upcoming features

  • New functionality allows cleanup of old driver files from the UIU Driver Database

  • Future: Foundation established for customer-driven UIU Driver Database controls to opt in/out of operating systems included in the UIU Repository

Introducing the UIU Plug-ins 2.0

The UIU Plug-ins 2.0 was designed to alleviate the demands of upgrading the UIU in complex MDT/SCCM environments. That said, The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT/SCCM (v1.x). The UIU plug-in (v1.x) products will receive limited support as deprecated versions and customers will be encouraged to upgrade to the fully supported UIU Plug-ins 2.0 product. The UIU Plug-ins 2.0 may be installed without removing the UIU v1.x product from an environment and will coexist without issue, even if both versions are utilizing the same source/deployment share. Updating the UIU Repository in a shared capacity should be migrated to use the UIU Plug-ins 2.0 technology as improvements have been made to ensure accuracy and quality. OS Deployment Task sequences should then be migrated by removing the task sequence element, UIU Machine Configuration, which is associated with the UIU v1.x product and adding the UIU Deployment Configuration element which is associated with the UIU 2.x product. During testing, it is acceptable for Administrators to disable the old element while testing the new element.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard SCCM Console interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

System Center Configuration Manager (SCCM)
In SCCM, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin" directory as well as the addition of necessary WMI classes (MOF) to support the UIU Plug-ins 2.0. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. Furthermore, if an Administrator is not able to control the configuration of various SCCM Remote Console implementations (distribution of a single UIU dll file), the integration of the UIU Plug-ins 2.0 may prove to be problematic and utilizing the Run Command Line task element will alleviate those issues.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support

2.2.0.0 - UIU Plug-ins 2.0 with MDT - Upgrade Release Bookmark



February 20, 2018
Includes UIUprep version 5.6.0.0


Please refer to the UIU Plug-ins 2.0 - MDT User Guides for detailed implementation and usage instructions.


This release of the UIU Plug-ins 2.0 includes general code review and clean-up.

The MDT and SCCM Plug-ins now accurately record the UIU License Key in their Task Sequence Properties (XML files). This change is cosmetic as the correct UIU License Key was already applied to the UIU task element.


Added support for MDT build 8450


Added support (specifically for Microsoft Deployment Toolkit (MDT), build 8450) in the LIVE & TRIAL versions of the UIU Plug-ins 2.0 for MDT's Installer and Updater applications to properly deliver the required version of the uiumdt.dll within the framework of the various versions of MDT, including:

  • MDT 2012 Update 1 - 6.1.2373.0
  • MDT 2013 - 6.2.5019.0
  • MDT 2013 Update 1 - 6.3.8290.1000
  • MDT 2013 Update 1 (re-released on Sept 15, 2015) - 6.3.8298.1000
  • MDT 2013 Update 2 - 6.3.8330.1000
  • Microsoft Deployment Toolkit (MDT), build 8443 - 6.3.8443.1000
  • Microsoft Deployment Toolkit (MDT), build 8450 - 6.3.8450.1000


Note:
As of Microsoft Deployment Toolkit (MDT), build 8443, Microsoft is deprecating the year and update version nomenclature on the naming of MDT revisions. For more information, click here.

To download Microsoft Deployment Toolkit (MDT), build 8450, click the following link:
Microsoft Deployment Toolkit (MDT) v6.3.8450.1000


REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

Features - MDT (as of version 2.0.0.0

  • More robust UIU Repository management with automated checks for integrity

  • Enhanced delivery of the UIU Driver Database

  • New and improved user interface

  • One-click opt-in access to unreleased features

  • New functionality allows cleanup of old driver files from the UIU Driver Database

  • Future: Foundation established for customer-driven UIU Driver Database controls to opt in/out of operating systems included in the UIU Repository

Introducing the UIU Plug-ins 2.0

The UIU Plug-ins 2.0 was designed to alleviate the demands of upgrading the UIU in complex MDT/SCCM environments. That said, The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT/SCCM (v1.x). The UIU plug-in (v1.x) products will receive limited support as deprecated versions and customers will be encouraged to upgrade to the fully supported UIU Plug-ins 2.0 product. The UIU Plug-ins 2.0 may be installed without removing the UIU v1.x product from an environment and will coexist without issue, even if both versions are utilizing the same source/deployment share. Updating the UIU Repository in a shared capacity should be migrated to use the UIU Plug-ins 2.0 technology as improvements have been made to ensure accuracy and quality. OS Deployment Task sequences should then be migrated by removing the task sequence element, UIU Machine Configuration, which is associated with the UIU v1.x product and adding the UIU Deployment Configuration element which is associated with the UIU 2.x product. During testing, it is acceptable for Administrators to disable the old element while testing the new element.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard MDT Deployment Workbench interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

Microsoft Deployment Toolkit (MDT)
In MDT, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Deployment Toolkit\bin" directory as well as a modification (additional section appended) to the Actions.xml file in the same directory. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support

DB-18-02-20 Driver Database Update Bookmark

February 20, 2018

Driver DB Amendments:

Customer-requested drivers since January 24, 2018 release.


Drivers Affected:

See Attached: UIU DB-18-02-20 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-18-02-20.pdf

Issue: Dell Latitude 6540 Hangs

Symptoms:
Dell Latitude 6540 Hangs upon setting up Video Settings.

Resolution:
Faulty AMD driver was removed from the UIU Driver Database.



Issue: Microsoft Surface Laptop BSOD

Symptoms:
Microsoft Surface Laptop would BSOD during mni-setup.

Resolution:
The Surface Laptop required additional IDs to be associated with the device in order differentiate its driver selection from other, similar Surface Pro 4 drivers.




Notice! -- HP Synaptics keylogger vulnerability --

We at Big Bang have been following the news regarding the Synaptics keylooger vulnerability associated with various HP laptop models.

If you become aware of a Synaptics driver that specifically addresses the keylogger vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

List of HP machines affected by the Synaptics keylogger issue: HPSBHF03564 rev 2 - Synaptics Touchpad Driver Potential, Local Loss of Confidentiality



WARNING! -- Regarding KRACK Wi-Fi vulnerability --

We at Big Bang have been following the news regarding the WPA2 hack known as Krack (key reinstallation attack).

During the week of October 16, 2017, researchers announced the discovery of a vulnerability which exploits the WPA2 protocol and allows attackers to steal sensitive information from unencrypted communications. It may also allow attackers to inject code (presumably malware) into websites.

"It’s important to keep the impact of KRACK in perspective: KRACK does not affect HTTPS traffic, and KRACK’s discovery does not mean all Wi-Fi networks are under attack."

The list of Wi-Fi vendors/chipset manfacturers is extensive and Big Bang is in the process of searching/monitoring each vendor for updates to their wi-fi network drivers tht specifically addresss the Krack vulnerability. This process is entirely subject to the availability of adequately-prepared drivers by the chipset manufacturers. We anticipate that this update will take place over a lengthy period of time and in fact, may not be realized for those vendors that are out of business, no longer supporting versions of chipsets or are not prepared to update their device drivers.

If you become aware of a wi-fi network driver that specifically addresses the Krack vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

For additional information, please refer to the following links:
KRACK Vulnerability: What You Need To Know
Key Reinstallation Attacks: Breaking WPA2 by forcing nonce reuse
Here’s what you can do to protect yourself from the KRACK WiFi vulnerability



WARNING! -- Windows 7/8/8.1 on Kaby Lake Intel and Bristol Ridge AMD Processors! --

Intel's seventh generation Core processors, the Kaby Lake series (I7-7xxx, I5-7xxx CPU description = Kaby Lake) as well as AMD Bristol Ridge 7th Generation , will only have Windows 10 x64 operating system support! There will be no legacy operating system support (Windows 7 or Windows 8.1) for Kaby Lake or Bristol Ridge equipped systems.

Big Bang has tested the deployment of Windows 7, Windows 8.1 and Windows 10 on several machines equipped with the Intel 7th Generation core processors and has found that, in our testing cases, all operating systems successfully deployed to those machines, (for which their architecture was applicable). Notwithstanding, Big Bang expects a decrease in or elimination of driver production/offering for non-Windows 10 x64 operating systems. Big Bang will take all reasonable measures to supply drivers for the affected hardware on non-compliant operating systems.

For additional information, please refer to the following links:
Lifecycle Policy FAQ—Windows products
Updates to Silicon Support Policy for Windows
Microsoft Windows Operating System support for Intel Kaby Lake processors
Microsoft blocks Kaby Lake and Ryzen PCs from Windows 7, 8 updates


NOTICE! -- UIU Classic users only! --

UIU Classic product v4.9.6.0 (or newer) is required to utilize UIU Driver Database versions newer than DB-17-01-26!


Reminder:

The full driver database exceeds 17Gb in size (17.6 Gb). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).



USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.


Support Reminder:

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!



2.1.0.0 - UIU Plug-ins 2.0 with MDT - Upgrade Release Bookmark



February 14, 2018
Includes UIUprep version 5.6.0.0


Please refer to the UIU Plug-ins 2.0 - MDT User Guides for detailed implementation and usage instructions.


This release of the UIU Plug-ins 2.0 includes general code review and clean-up.


REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

Features - MDT (as of version 2.0.0.0)

  • More robust UIU Repository management with automated checks for integrity

  • Enhanced delivery of the UIU Driver Database

  • New and improved user interface

  • One-click opt-in access to unreleased features

  • New functionality allows cleanup of old driver files from the UIU Driver Database

  • Future: Foundation established for customer-driven UIU Driver Database controls to opt in/out of operating systems included in the UIU Repository

Introducing the UIU Plug-ins 2.0

The UIU Plug-ins 2.0 was designed to alleviate the demands of upgrading the UIU in complex MDT/SCCM environments. That said, The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT/SCCM (v1.x). The UIU plug-in (v1.x) products will receive limited support as deprecated versions and customers will be encouraged to upgrade to the fully supported UIU Plug-ins 2.0 product. The UIU Plug-ins 2.0 may be installed without removing the UIU v1.x product from an environment and will coexist without issue, even if both versions are utilizing the same source/deployment share. Updating the UIU Repository in a shared capacity should be migrated to use the UIU Plug-ins 2.0 technology as improvements have been made to ensure accuracy and quality. OS Deployment Task sequences should then be migrated by removing the task sequence element, UIU Machine Configuration, which is associated with the UIU v1.x product and adding the UIU Deployment Configuration element which is associated with the UIU 2.x product. During testing, it is acceptable for Administrators to disable the old element while testing the new element.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard MDT Deployment Workbench interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

Microsoft Deployment Toolkit (MDT)
In MDT, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Deployment Toolkit\bin" directory as well as a modification (additional section appended) to the Actions.xml file in the same directory. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support

2.1.0.0 - UIU Plug-ins 2.0 with SCCM - Upgrade Release Bookmark



February 14, 2018
Includes UIUprep version 5.6.0.0


Please refer to the UIU Plug-ins 2.0 - SCCM User Guides for detailed implementation and usage instructions.


This release of the UIU Plug-ins 2.0 includes general code review and clean-up.

The UIU Plug-ins 2.0 for SCCM version 2.1.0.0 also includes support for 1E Nomad/Active Efficiency. Please contact UIU Support for details.

REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

Features - SCCM (as of version 2.0.0.0)

  • More robust UIU Repository management with automated checks for integrity

  • Enhanced delivery of the UIU Driver Database

  • Improved integration with SCCM native controls

  • New hybrid methodology for Content Delivery, reducing bandwidth and local storage needs while decreasing driver acquisition times during OS Deployment Task Sequence

  • New and improved user interface

  • Ability to create and manage the UIU Repository from any administrator PC

  • One-click opt-in access to unreleased upcoming features

  • New functionality allows cleanup of old driver files from the UIU Driver Database

  • Future: Foundation established for customer-driven UIU Driver Database controls to opt in/out of operating systems included in the UIU Repository

Introducing the UIU Plug-ins 2.0

The UIU Plug-ins 2.0 was designed to alleviate the demands of upgrading the UIU in complex MDT/SCCM environments. That said, The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT/SCCM (v1.x). The UIU plug-in (v1.x) products will receive limited support as deprecated versions and customers will be encouraged to upgrade to the fully supported UIU Plug-ins 2.0 product. The UIU Plug-ins 2.0 may be installed without removing the UIU v1.x product from an environment and will coexist without issue, even if both versions are utilizing the same source/deployment share. Updating the UIU Repository in a shared capacity should be migrated to use the UIU Plug-ins 2.0 technology as improvements have been made to ensure accuracy and quality. OS Deployment Task sequences should then be migrated by removing the task sequence element, UIU Machine Configuration, which is associated with the UIU v1.x product and adding the UIU Deployment Configuration element which is associated with the UIU 2.x product. During testing, it is acceptable for Administrators to disable the old element while testing the new element.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard SCCM Console interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

System Center Configuration Manager (SCCM)
In SCCM, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin" directory as well as the addition of necessary WMI classes (MOF) to support the UIU Plug-ins 2.0. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. Furthermore, if an Administrator is not able to control the configuration of various SCCM Remote Console implementations (distribution of a single UIU dll file), the integration of the UIU Plug-ins 2.0 may prove to be problematic and utilizing the Run Command Line task element will alleviate those issues.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support

5.6.0.0 - Executables Update Only Bookmark

February 14, 2018
Includes UIUprep version 5.6.0.0


Updating from pre-5.5.0.0 versions of the UIU 5 product requires two steps. First, use the UIU 5 Updater to obtain the 5.5.0.0 version and then re-execute online updates from that version to obtain UIU 5 (v5.6.0.0)


Feature Change - Renewed User Interface

Version 5.6.0.0 includes an all-new GUI for the UIU 5

The side bar has been replaced with a standard menu bar. Please review the UIU 5 User Guide for specifics as some features have been re-arranged for clarity.

All Deployment Solution-specific wizards are now located under the Deployment Integration menu option.

Feature Addition - WinPE Boot+

The ability to "Clear DriverStore" (selected by default) has been added. This feature removes any non-inbox drivers from the selected .WIM image before adding new (UIU) boot-critical drivers, which are now limited to the selected OS/Architecture.

Feature Enhancement - Repository Management

Improvements have been made to Repository Management in this version and now include the ability to update any combination of UIU Components, Driver Database, and Driver Files. Additional improvements include the aility to perform CRC Validation, Clean up unreferenced drivers, and produce commands that will facilitate the scripting of updates, (e.g. using scheduled tasks).

Issue: Repository Management - “Update Repository” function

Symptoms:
User cannot create a new UIU Repository using the “Update Repository” function.

Resolution:
Fixed a bug that was preventing the Repository Manager from being able to properly generate a UIU Repository from an empty (or incomplete) repository.



Issue: UNC path Handling

Symptoms:
The UIU 5 Console was not properly inserting quotes for UNC Path names that included a space, causing UIUPrep to fail during deployment.

Resolution:
Fixed an issue that did not wrap deployment wizard UIUPrep commands in quotes, which could lead to deployment integrations not being able to invoke UIUPrep for users whom have UIU Repositories on UNC Paths that include a space in the path.



Issue: WinPE Boot+ Failures

Symptoms:
WinPE Boot+ provided all boot-critical drivers, regardless of OS and architecture which could create issues when booting.

Resolution:
The WinPE Boot+ feature now analyzes the provided .WIM image and only boot-critical drivers that meet the OS version and architecture are included. This should make the process of using WinPE Boot+ much faster, as well as much more reliable.



The UIU 5 (version 5.5.0.0 and newer) no longer employs driver.dat files for installation and manual updates. This (and future) versions will require Driver.imp files (e.g. DB170411-p5460.imp) for those operations. Online UIU 5 Updates will be unaffected.


UIU Log File Location CHANGE!

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.



DB-18-01-24 Driver Database Update Bookmark

January 24, 2018

Driver DB Amendments:

Customer-requested drivers since January 11, 2018 release.


Drivers Affected:

See Attached: UIU DB-18-01-24 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-18-01-24.pdf


Notice! -- HP Synaptics keylogger vulnerability --

We at Big Bang have been following the news regarding the Synaptics keylooger vulnerability associated with various HP laptop models.

If you become aware of a Synaptics driver that specifically addresses the keylogger vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

List of HP machines affected by the Synaptics keylogger issue: HPSBHF03564 rev 2 - Synaptics Touchpad Driver Potential, Local Loss of Confidentiality



WARNING! -- Regarding KRACK Wi-Fi vulnerability --

We at Big Bang have been following the news regarding the WPA2 hack known as Krack (key reinstallation attack).

During the week of October 16, 2017, researchers announced the discovery of a vulnerability which exploits the WPA2 protocol and allows attackers to steal sensitive information from unencrypted communications. It may also allow attackers to inject code (presumably malware) into websites.

"It’s important to keep the impact of KRACK in perspective: KRACK does not affect HTTPS traffic, and KRACK’s discovery does not mean all Wi-Fi networks are under attack."

The list of Wi-Fi vendors/chipset manfacturers is extensive and Big Bang is in the process of searching/monitoring each vendor for updates to their wi-fi network drivers tht specifically addresss the Krack vulnerability. This process is entirely subject to the availability of adequately-prepared drivers by the chipset manufacturers. We anticipate that this update will take place over a lengthy period of time and in fact, may not be realized for those vendors that are out of business, no longer supporting versions of chipsets or are not prepared to update their device drivers.

If you become aware of a wi-fi network driver that specifically addresses the Krack vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

For additional information, please refer to the following links:
KRACK Vulnerability: What You Need To Know
Key Reinstallation Attacks: Breaking WPA2 by forcing nonce reuse
Here’s what you can do to protect yourself from the KRACK WiFi vulnerability



WARNING! -- Windows 7/8/8.1 on Kaby Lake Intel and Bristol Ridge AMD Processors! --

Intel's seventh generation Core processors, the Kaby Lake series (I7-7xxx, I5-7xxx CPU description = Kaby Lake) as well as AMD Bristol Ridge 7th Generation , will only have Windows 10 x64 operating system support! There will be no legacy operating system support (Windows 7 or Windows 8.1) for Kaby Lake or Bristol Ridge equipped systems.

Big Bang has tested the deployment of Windows 7, Windows 8.1 and Windows 10 on several machines equipped with the Intel 7th Generation core processors and has found that, in our testing cases, all operating systems successfully deployed to those machines, (for which their architecture was applicable). Notwithstanding, Big Bang expects a decrease in or elimination of driver production/offering for non-Windows 10 x64 operating systems. Big Bang will take all reasonable measures to supply drivers for the affected hardware on non-compliant operating systems.

For additional information, please refer to the following links:
Lifecycle Policy FAQ—Windows products
Updates to Silicon Support Policy for Windows
Microsoft Windows Operating System support for Intel Kaby Lake processors
Microsoft blocks Kaby Lake and Ryzen PCs from Windows 7, 8 updates


NOTICE! -- UIU Classic users only! --

UIU Classic product v4.9.6.0 (or newer) is required to utilize UIU Driver Database versions newer than DB-17-01-26!


Reminder:

The full driver database exceeds 17Gb in size (17.2 Gb). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).



USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.


Support Reminder:

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!



DB-18-01-11 Driver Database Update Bookmark

January 11, 2018

Driver DB Amendments:

Customer-requested drivers since January 2, 2018 release.


Drivers Affected:

See Attached: UIU DB-18-01-11 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-18-01-11.pdf


Notice! -- HP Synaptics keylogger vulnerability --

We at Big Bang have been following the news regarding the Synaptics keylooger vulnerability associated with various HP laptop models.

If you become aware of a Synaptics driver that specifically addresses the keylogger vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

List of HP machines affected by the Synaptics keylogger issue: HPSBHF03564 rev 2 - Synaptics Touchpad Driver Potential, Local Loss of Confidentiality



WARNING! -- Regarding KRACK Wi-Fi vulnerability --

We at Big Bang have been following the news regarding the WPA2 hack known as Krack (key reinstallation attack).

During the week of October 16, 2017, researchers announced the discovery of a vulnerability which exploits the WPA2 protocol and allows attackers to steal sensitive information from unencrypted communications. It may also allow attackers to inject code (presumably malware) into websites.

"It’s important to keep the impact of KRACK in perspective: KRACK does not affect HTTPS traffic, and KRACK’s discovery does not mean all Wi-Fi networks are under attack."

The list of Wi-Fi vendors/chipset manfacturers is extensive and Big Bang is in the process of searching/monitoring each vendor for updates to their wi-fi network drivers tht specifically addresss the Krack vulnerability. This process is entirely subject to the availability of adequately-prepared drivers by the chipset manufacturers. We anticipate that this update will take place over a lengthy period of time and in fact, may not be realized for those vendors that are out of business, no longer supporting versions of chipsets or are not prepared to update their device drivers.

If you become aware of a wi-fi network driver that specifically addresses the Krack vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

For additional information, please refer to the following links:
KRACK Vulnerability: What You Need To Know
Key Reinstallation Attacks: Breaking WPA2 by forcing nonce reuse
Here’s what you can do to protect yourself from the KRACK WiFi vulnerability



WARNING! -- Windows 7/8/8.1 on Kaby Lake Intel and Bristol Ridge AMD Processors! --

Intel's seventh generation Core processors, the Kaby Lake series (I7-7xxx, I5-7xxx CPU description = Kaby Lake) as well as AMD Bristol Ridge 7th Generation , will only have Windows 10 x64 operating system support! There will be no legacy operating system support (Windows 7 or Windows 8.1) for Kaby Lake or Bristol Ridge equipped systems.

Big Bang has tested the deployment of Windows 7, Windows 8.1 and Windows 10 on several machines equipped with the Intel 7th Generation core processors and has found that, in our testing cases, all operating systems successfully deployed to those machines, (for which their architecture was applicable). Notwithstanding, Big Bang expects a decrease in or elimination of driver production/offering for non-Windows 10 x64 operating systems. Big Bang will take all reasonable measures to supply drivers for the affected hardware on non-compliant operating systems.

For additional information, please refer to the following links:
Lifecycle Policy FAQ—Windows products
Updates to Silicon Support Policy for Windows
Microsoft Windows Operating System support for Intel Kaby Lake processors
Microsoft blocks Kaby Lake and Ryzen PCs from Windows 7, 8 updates


NOTICE! -- UIU Classic users only! --

UIU Classic product v4.9.6.0 (or newer) is required to utilize UIU Driver Database versions newer than DB-17-01-26!


Reminder:

The full driver database exceeds 17Gb in size (17.1 Gb). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).



USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.


Support Reminder:

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!



DB-18-01-02 Driver Database Update Bookmark

January 2, 2018

Driver DB Amendments:

Customer-requested drivers since December 15, 2017 release.


Drivers Affected:

See Attached: UIU DB-18-01-02 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-18-01-02.pdf

Driver Refresh: Intel Graphics drivers

Details:
Phase 1 of the cleanup and refresh of UIU-supplied Intel graphics drivers. We've removed drivers that would not be selected through the Windows enumeration process and added the latest Intel graphics drivers to accommodate newer hardware. As graphics drivers are typically large, this reduction in total UIU-supplied graphics drivers will decrease the UIU Driver Database by approximately 2Gb in Phase 1. Please contact Big Bang Support if you notice aberrations in graphics support on Intel hardware or if you require additional information on reducing the footprint of the UIU Repository.




Notice! -- HP Synaptics keylogger vulnerability --

We at Big Bang have been following the news regarding the Synaptics keylooger vulnerability associated with various HP laptop models.

If you become aware of a Synaptics driver that specifically addresses the keylogger vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

List of HP machines affected by the Synaptics keylogger issue: HPSBHF03564 rev 2 - Synaptics Touchpad Driver Potential, Local Loss of Confidentiality



WARNING! -- Regarding KRACK Wi-Fi vulnerability --

We at Big Bang have been following the news regarding the WPA2 hack known as Krack (key reinstallation attack).

During the week of October 16, 2017, researchers announced the discovery of a vulnerability which exploits the WPA2 protocol and allows attackers to steal sensitive information from unencrypted communications. It may also allow attackers to inject code (presumably malware) into websites.

"It’s important to keep the impact of KRACK in perspective: KRACK does not affect HTTPS traffic, and KRACK’s discovery does not mean all Wi-Fi networks are under attack."

The list of Wi-Fi vendors/chipset manfacturers is extensive and Big Bang is in the process of searching/monitoring each vendor for updates to their wi-fi network drivers tht specifically addresss the Krack vulnerability. This process is entirely subject to the availability of adequately-prepared drivers by the chipset manufacturers. We anticipate that this update will take place over a lengthy period of time and in fact, may not be realized for those vendors that are out of business, no longer supporting versions of chipsets or are not prepared to update their device drivers.

If you become aware of a wi-fi network driver that specifically addresses the Krack vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

For additional information, please refer to the following links:
KRACK Vulnerability: What You Need To Know
Key Reinstallation Attacks: Breaking WPA2 by forcing nonce reuse
Here’s what you can do to protect yourself from the KRACK WiFi vulnerability



WARNING! -- Windows 7/8/8.1 on Kaby Lake Intel and Bristol Ridge AMD Processors! --

Intel's seventh generation Core processors, the Kaby Lake series (I7-7xxx, I5-7xxx CPU description = Kaby Lake) as well as AMD Bristol Ridge 7th Generation , will only have Windows 10 x64 operating system support! There will be no legacy operating system support (Windows 7 or Windows 8.1) for Kaby Lake or Bristol Ridge equipped systems.

Big Bang has tested the deployment of Windows 7, Windows 8.1 and Windows 10 on several machines equipped with the Intel 7th Generation core processors and has found that, in our testing cases, all operating systems successfully deployed to those machines, (for which their architecture was applicable). Notwithstanding, Big Bang expects a decrease in or elimination of driver production/offering for non-Windows 10 x64 operating systems. Big Bang will take all reasonable measures to supply drivers for the affected hardware on non-compliant operating systems.

For additional information, please refer to the following links:
Lifecycle Policy FAQ—Windows products
Updates to Silicon Support Policy for Windows
Microsoft Windows Operating System support for Intel Kaby Lake processors
Microsoft blocks Kaby Lake and Ryzen PCs from Windows 7, 8 updates


NOTICE! -- UIU Classic users only! --

UIU Classic product v4.9.6.0 (or newer) is required to utilize UIU Driver Database versions newer than DB-17-01-26!


Reminder:

The full driver database exceeds 17Gb in size (17.1 Gb). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).



USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.


Support Reminder:

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!



DB-17-12-15 Driver Database Update Bookmark

December 15, 2017

Driver DB Amendments:

Customer-requested drivers since December 1, 2017 release.


Drivers Affected:

See Attached: UIU DB-17-12-15 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-17-12-15.pdf

Issue: Intel Graphics Driver for Windows

Symptoms:
Specific medical-grade machines experienced graphics related difficulties.

Resolution:
Added a specific Intel-prepared graphics driver to accomodate specific machines.
Intel Graphics Driver for Windows* [15.45]



Driver Refresh: HP Synaptics touchpad drivers

Details:
HP recommended update of Synaptics touchpad drivers due to keylogger vulnerability.
Synaptics Touchpad Driver Potential, Local Loss of Confidentiality




Notice! -- HP Synaptics keylogger vulnerability --

We at Big Bang have been following the news regarding the Synaptics keylooger vulnerability associated with various HP laptop models.

If you become aware of a Synaptics driver that specifically addresses the keylogger vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

List of HP machines affected by the Synaptics keylogger issue: HPSBHF03564 rev 2 - Synaptics Touchpad Driver Potential, Local Loss of Confidentiality



WARNING! -- Regarding KRACK Wi-Fi vulnerability --

We at Big Bang have been following the news regarding the WPA2 hack known as Krack (key reinstallation attack).

During the week of October 16, 2017, researchers announced the discovery of a vulnerability which exploits the WPA2 protocol and allows attackers to steal sensitive information from unencrypted communications. It may also allow attackers to inject code (presumably malware) into websites.

"It’s important to keep the impact of KRACK in perspective: KRACK does not affect HTTPS traffic, and KRACK’s discovery does not mean all Wi-Fi networks are under attack."

The list of Wi-Fi vendors/chipset manfacturers is extensive and Big Bang is in the process of searching/monitoring each vendor for updates to their wi-fi network drivers tht specifically addresss the Krack vulnerability. This process is entirely subject to the availability of adequately-prepared drivers by the chipset manufacturers. We anticipate that this update will take place over a lengthy period of time and in fact, may not be realized for those vendors that are out of business, no longer supporting versions of chipsets or are not prepared to update their device drivers.

If you become aware of a wi-fi network driver that specifically addresses the Krack vulnerability and you suspect that we have not yet encountered that driver, please bring it to the immediate attention of Big Bang Support.

Thank you for your patience and assistance.

For additional information, please refer to the following links:
KRACK Vulnerability: What You Need To Know
Key Reinstallation Attacks: Breaking WPA2 by forcing nonce reuse
Here’s what you can do to protect yourself from the KRACK WiFi vulnerability



WARNING! -- Windows 7/8/8.1 on Kaby Lake Intel and Bristol Ridge AMD Processors! --

Intel's seventh generation Core processors, the Kaby Lake series (I7-7xxx, I5-7xxx CPU description = Kaby Lake) as well as AMD Bristol Ridge 7th Generation , will only have Windows 10 x64 operating system support! There will be no legacy operating system support (Windows 7 or Windows 8.1) for Kaby Lake or Bristol Ridge equipped systems.

Big Bang has tested the deployment of Windows 7, Windows 8.1 and Windows 10 on several machines equipped with the Intel 7th Generation core processors and has found that, in our testing cases, all operating systems successfully deployed to those machines, (for which their architecture was applicable). Notwithstanding, Big Bang expects a decrease in or elimination of driver production/offering for non-Windows 10 x64 operating systems. Big Bang will take all reasonable measures to supply drivers for the affected hardware on non-compliant operating systems.

For additional information, please refer to the following links:
Lifecycle Policy FAQ—Windows products
Updates to Silicon Support Policy for Windows
Microsoft Windows Operating System support for Intel Kaby Lake processors
Microsoft blocks Kaby Lake and Ryzen PCs from Windows 7, 8 updates


NOTICE! -- UIU Classic users only! --

UIU Classic product v4.9.6.0 (or newer) is required to utilize UIU Driver Database versions newer than DB-17-01-26!


Reminder:

The full driver database exceeds 19Gb in size (19.3 Gb). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).



USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.


Support Reminder:

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!