[TimShriver]

Hi Rob,

Yes HALi required a change that caused use to break compatibility. It turns out the QuickInit routine did not initialize some of the areas it was intended to init. So it was a tough call but we thought it was more important that the init areas outlined in the HALi documentation were actually performed.

We have had a couple of reports from customers regarding HAL after a recent windows update. We are trying to identify the common thread between the 3 reports we have, so more data would be great. What we have tried to collect are the typical HAL configuration information along with the hardware and OS details.

Thank you,

Tim