Ran into a new problem but I am not sure if it related to the creators update. Its highly suspect.
I have a custom board inside the PC that I talk to using LabVIEW. When I bought the new PC, I switched over to using their driver Wizard tool. This creates the INF and INI files. I then talk directly to the board using LabVIEW built-in functions.
I went to run it and was able to read and write to the board just fine. Everything worked normal, except there were no interrupts. I did not suspect the hardware would fail and cause this. I had made no changes to the code since I ported over to with the new PC. When I would attempt to enable the events triggered by the hardware interrupt, LabVIEW will error with a code that had very little information on. Size mismatch or such.
After various tests and having no luck, I was going to reinstall the hardware in the old P4 machine just to make sure it was not really a hardware problem. Instead, I decided to recreate the INF/INI files from scratch. The tool I used is the same version. The two files match with the old ones. I attempted to update the driver to new (even though it was identical) and Windows 10 would not allow it because of the signature. I used the shift restart/seven to override this. And bingo, it all starts working.
I don't install a lot of software on this PC. The only other thing that was new was I had to upgrade VirtualBox after the creators update. It makes no sense that MS would have scrubbed the settings and disabled the interrupts. Yet, I can't explain why this happened. Maybe when they were blue screening my PC with their latest spyware, Candy Crush X-box updates, they disabled the hardware as part of the recovery.