False alarm. I have installed new Win10, and now everything working great. The question is what peace of software killed netinstall last time. I will do step by step app install...
This is going to sound stupid... but have you tried changing its name?
After installing Windows 10, I had the same problem -- devices wouldn't show up in the netinstall window. I had a static IP set. I had it set to always run as administrator. I had all other networking turned off. I updated the drivers for my USB-to-ethernet adapter. I double-checked the presence of the firewall hole.I scanned the boot IP range from the attached MikroTik, and the boot server showed up. But it just would not work
As a related problem, I was getting really tired of seeing the warning box saying, "Do you want to allow this app from an unknown publisher to modify your system?" before every failed test, so I did a web search to see if there were any way to turn that off. I came across this posting
, where a fellow claimed that any app with the strings patch, install, update, or setup in the name will trigger this warning, while others won't.
It smacked of voodoo, but I renamed the package to netinstt
all.exe. And not only did it turn off that message, but damned if netinstall didn't immediately start working (after one additional, "do you want to let this app through the firewall" message box).
Hey, I can't explain it, but it's working now, and I'm not going to screw with it.