after long experimenting, desperately trying to recover/un-brick 3 of my lifeless mikrotik babies by using NetInstall i was discovering(testing thru Win2000 to Win10) that its not work properly in Windows versions above Win7.
even if you disable BFE and firewall, even if you booth in “safe mode with networking”, whatever
(not tried WinPE or OTG modes, yet)
also in XP you need to disable firewall and in Windows 7 you need to disable BOTH “Base Filtering Engine” and “Firewall” services(and some other relevant, like anti-virus programs, and anything else netflow-relevant/tampering)
my suggestion is: is any chance to make it compatible with actual version of Windows, again? please
p.s.
i can only guess about what affected, its may be windows components change, but more likely difference between NDIS 6.1, NDIS 6.0, NDIS 5.1 and used in win8/8.1/10 NDIS 6.30, NDIS 6.40 somehow.
I hadn’t often use Netinstall, but never had any troubles on Win7/8.1/10. I don’t turn off any services and just allow Windows firewall to add it in whitelist.
weird. i tested different machines - win above w7 failed to properly run netinstall(even wih “comatibility” modes, even in “safe mode with networking”.
do you use untouched 'from box" windows or real-world boxes affected by Windows Update ?
p.s. i wasn’t tested NIC NDIS 6.0, NDIS 6.1 drivers over Win8/8.1./10 yet, but suspect they may work, compared to updated (and Windows stock drivers for).
Second ones, sequently updatable by Windows Update. Last time I used it on Win10, just run it as administrator, set up the device’s IP (hAP lite), and after powering the hAP lite in netinstall mode I’ve seen it in Netinstall window.
This tool is not 100% solid, but I always got what I wanted, with single or multiple tries.
not worked on my Win10. both from “fresh|” install or after WU updating it to actual. TH2.17
both “run as administrator”(from administrator profile) and playing with "compatibility, “safe mode with networking” and other usuall/common tricks/workarounds - didn’t helped/worked too.
Hello!
I, too, when the router firmware does not start. I installed Windows 10 pro 64bit. I enjoyed the different instructions, but nothing helped. You can not disable the firewall. It is necessary to add to the firewall exceptions for netinstall, in the anti-virus too. Run as administrator. Once the program finds the first device firmware can be nothing happen (a process will not start). In this case, you must close the NetInstall and run it again, it will immediately and device firmware must succeed.
PS: If you have a damaged boot sector can take advantage of back-up, instructions are in the manual Wiki.
one of my co-workers speculated thats it may be impact of AMD CPU’s(nearly 1/3 used in desktops, aside engineers) or Realtek-branded Phy/NIC in motherboards(and/or combination of both).
would test it out when i get enough notebooks with atheros and intel CPU’s (those that around me - not fit, sadly .
another speculation was “it shouldn’t work in 64-bit versions over WoW” which i can’t test too, since there was no even single PC with 32-bit Windows around me
I think it’s probably going to be related to the ethernet card and driver that you’re using.
I had troubles with Netinstall (and neighbor discovery with the … button in Winbox) on my desktop XP machine at my last job, but my laptop ran the same version of XP, but was completely able to perform these tasks. (I hated having to go un-bag my laptop every time I wanted to run Netinstall). Even more interesting was the fact that my workstation had two NICs - the primary and the lab. Guess what - the primary NIC worked for netinstall / neighbor discovery.
EDIT: I never did fix the problem, I just lived with it, satisfied that I knew why it was acting that way, but not sufficiently annoyed to bother digging into drivers, etc.
seems like it’s because both those tools use first enumerated NIC and work only with it. if you disable one NIC - second one starts to work automagically
lucky you.
do you had PC with AMD CPU and Realtek NIC ?
32-bit versions seems working (tested on OTG versions and in “plain” windows).
also seems intel CPU/PC owners do complain less about netinstall, judging from forums perspective.
.