Initialize hardware does not always return error for invalid hardware ID

[dbendele]

Describe the bug
Source\Custom Device Support\Hardware API\Finalize Hardware.vi returns an error on first run, but then it returns no error (which ironically fails the new test VI: test Initialize and Finalize Hardware_Invalid Module

To Reproduce
Steps to reproduce the behavior:

1. Run the old test multiple times, or run the new test (before modifications)
2. Note that first iteration produces the expected error 404043
3. Note that the next iteration finds the hardware resource (which should not have been there), and so skips the board open call which produces error 404043 for invalid hardware ID.

Expected behavior
The same error should happen on reset, no reset, force close, no force close regardless of the previous state.

Screenshots
Heart of the problem is in this case of an AIM VI we wrap:

where it can be seen that a remove instance call can add a resource that wasn't found. This is a bug that will also be reported to AIM even though their high-level API doesn't produce the error on/error off behavior reported here.

Desktop (please complete the following information):

• OS: Windows
• Version: 10 Pro (running in test mode)

Additional context
Add any other context about the problem here.