There have been several types of problems witnessed with the new release of Windows that has started to be distributed to customers as of 30 April 2018. We have seen several tricks that have helped in certain circumstances that we want to share with you. This is a living document, as more solutions become available (and we have tried them), we will update this document, so stay tuned! If you have seen something that has helped, add to the discussion, the more we know, the faster we can recover!
WSJT-X No audio
After the 1803 update, many WSJT-X users are losing input audio to their program. Usually, they can output tones, its just that the assigned DAX Channel does not cause audio to be received by the program.
The WSJT-X reflector has reported that a simple trick can solve this!
Go to the Settings page in Windows 10.
Click on Privacy.
Then select Microphone from the menu on the left side.
Check the box titled "Allow apps to access your microphone.
You will then have to decide which other, if any, apps need to be turned off or on (Camera, Cortana, etc.).
Missing DAX Sound Devices
Lou Detrich found that post-installation he was missing DAX IQ RX 1 sound device. He went to the Sounds control panel app and saw signal deflection on the reserved DAX device channel for DAX IQ 1 (DAX Reserved IQ RX 1) and that it has appropriate signal levels on it.
When he was looking for the DAX IQ RX 1, he saw that it was present, but mis-labeled as DAX Audio RX 1.
You can see that the descriptive text actually says the device is for DAX IQ but the name of it is DAX Audio RX 1.
Al, K0VM, had a similar problem and he just editted the name of the device after double-clicking it from the Sounds panel window. He changed it to the proper name.
Then, he clicked OK and rebooted his system. When it rebooted, it solved his problem!
DAX Devices do not load drivers correctly
We have seen one instance where the customer was uninstalling and installing his DAX drivers (he was getting the driver error dialog when DAX started). If you go to the Device Manager and look under Sound, Video and Game controllers, you would see the 4 DAX devices with a yellow triangle, indicated they were not properly loaded. If you double-click on one, you will see error text that reflects that the boot image was damaged or corrupted.
This can be caused by a new security feature, introduced in the 1803 release for Win10 Pro customers (and possibly Win10 Home customerms) called Device Guard. To see if you have Device Guard active, go to Settings and click on Updates and Security. In the left tab, click on Windows Security. In the right panel, click on Device Security.
If you see a window like below, you have no problem
There are several dependencies needed to support Device Guard, and you luckily do not qualify!
However, if you see something like below, you need to take action!
You can try to turn off Memory integrity by clicking the switch above. If it turns off, you are done. The system we saw with this would not allow us to turn it off. There is a reg file available that can turn it off.
Download and double-click the reg file, then reboot your system.
We will add more to this list as more knowledge becomes available.
Become part of this effort, let us know how you solved problems with 1803!