NAS Navigator 2 Communication Error

[bobsofine409]

A few days ago NAS Navigator 2 (V2.8.2) experienced and unexpected exit. The fault code was 0xC0000417. I believe that this references an invalid C-Runtime parameter. Since then NAS Navigator shows communications errors when trying to access the two NAS units on my network. The NAS units are fine, they are operating with no problems. NAS Navigator is working fine on the two other PCs on my network. My OS is the latest build of windows 10 and fully updated. The last time is used NAS Navigator (on 4/13) it was working fine. I'm using Norton AV and have tried shutting down the firewall but this does not help. Any thoughts on how I can restore NAS Navigator 2 to a working state.

[davo]

I am assuming you have tried a simple uninstall/reinstall of the software? Running the latest version of Win10 Pro here and no issues.

[bobsofine409]

Yup several times. Tried turning off AV and firewall. Navigator works just fine on three other PCs on my network. Tried SFC to repair any damaged files but no luck. It worked fine the last time I ran a full disk back up on 4/13. I'm really stumped on this one. I've posted a thread on the Win 10 users form but no luck there either. Win 10 is know for being freakey with network protocols so I'll be taking a close look at those but connections between this PCs and my other PCs is fine. It looks like something may be blocking the responses from the NAS units to Navigator.  Do you have any insight on anything I can check along this line?

[Eastmarch]

Can you do a system restore back to a date it was working? Sounds like a corrupted registry setting to me.

http://windows.microsoft.com/en-us/windows-10/windows-10-recovery-options#

Using a system restore point.

[bobsofine409]

I only have 1 restore point that is only 3 days old and that didn't help.
I looked thru the registries for both PCs and didn't see any obvious differences in any of the keys the reference "Buffalo."
NAS Navi appears to take a long time to find the NAS units so I think it is waiting for the units to send info on any errors after the identification. So I'm wondering what might be gumming up the works?  I looked top see if there were any differences between the two PCs insofar as services but I found none.
I could always do an in place repair/upgrade after I run a full backup image I suppose. There is a chance that might fix whatever has become corrupted, if that is the cause.
Any other thoughts?

Update 2016-05-12: I discovered the solution in Task Manager. Both "NASNavigator2" and "NAS Function Scheduling Application" had been disabled. Enabling them solved the problem. I probably disabled them last month in an effort to decrease boot time. In hindsight the time impact was probably impercptible.