Just received a pair of pre-paired nRAYs, the "Wireless Wire" kit.
Followed the directions here: https://help.mikrotik.com/docs/display/UM/nRAY+series
Grabbed laptop, set it's IP to 192.168.88.100, plugged straight into the master, changed its static IP to my LAN subnet using WinBox. Got it onto my LAN no fuss no muss.
Sat down at my main PC and using WinBox could not get the Quick Set upgrade feature to work, it complained about no internet access. So I upgraded manually by downloading routeros-7.13.2-arm64.npk and dragging it into the root of the files window, then rebooting, in accordance with the ROS doc's.
The nRAY came back up indicating 7.13.2 and could now find the internet, but there are no longer any entries in WinBox for the W60G radio and all of the pre-paired 60G radio config. is gone.

What did I do wrong and what are my next steps, please?

What you did wrong: manually upgrade by dropping package on Files.
What you should have done: upgrade through CLI or Winbox, then there would have been 1 package more on your device.

Since 7.13 routeros base package does NOT include legacy wireless drivers anymore (which are needed for 60G radios).
So you need to add wireless package as well.

• Install package
• Reboot
• Reset to default config
• Start config

WORST CASE:

• netinstall using 7.12
• upgrade (through CLI or Winbox) to 7.13.x

Could be someone actually using this device might chime in with better options.

See here for more info (release notes, helps sometimes to read them ):
viewtopic.php?t=202423

2. Drivers for older wireless and 60GHz interfaces, as well as the wireless management system CAPsMAN, are now part of a separate "wireless" package instead of being a part of the bundle package. This package can be uninstalled if not needed.

You do need it. So add it.

What you did wrong: manually upgrade by dropping package on Files.
What you should have done: upgrade through CLI or Winbox, then there would have been 1 package more on your device.

I tried to do it via WinBox but the delivered config. 6.xxx (can't remember the exact version) refused to perform the auto-update. I found the instructions online to do the drag and drop method. That method worked 100% fine.

Since 7.13 routeros base package does NOT include legacy wireless drivers anymore (which are needed for 60G radios).
So you need to add wireless package as well.

• Install package
• Reboot
• Reset to default config
• Start config

I'm new to MicroTik (but an old hand at Unifi). When I looked at the list of the two packages, I had thought it was "either/or", not "both". At least it was a basic error

Easily fixed. I had already rebooted after loading the updated RouterOS. I drag and dropped the wireless package, rebooted, and all is well, configuration was preserved.

Question for the future: when more than one package needs to be loaded can they both be dropped into the files window prior to a reboot, or is it first package-reboot-second package-reboot?

Thanks!

I tried to do it via WinBox but the delivered config. 6.xxx (can't remember the exact version) refused to perform the auto-update. I found the instructions online to do the drag and drop method. That method worked 100% fine.

Except ... with 7.13 comes the requirement you FIRST have to upgrade to 7.12.x and only THEN 7.13 will automatically take care of missing packages, transfer of wifi/wireless config to the right place etc.
It's clearly mentioned in the release notes for 7.13 which few seem to read.

Question for the future: when more than one package needs to be loaded can they both be dropped into the files window prior to a reboot, or is it first package-reboot-second package-reboot?

Depends but most of the times, both at the same time will do.
But upgrade using CLI or Winbox/Webfig is always better in case some "behind-the-scenes-stuff" needs to happen (see response above).

This is an absolute joke. I have been working with equipment like this for over 10 years and never had a problem with a core packaged item being left out of a firmware upgrade. They should stamp warnings on each of the subsequent "stable releases". I have never had an issue dropping a package into a file via winbox. The direction this company is going is really upsetting. I chose upload and uploaded it into winbox after I had downloaded from website and wireless package was left out. I also don't put my infrastructure on the internet, so that is a pretty stupid thing to do, they are doing that to try to force people to use the WIFI interface menu

To clarify its not in the release notes for anything higher than 7.13

This is an absolute joke.

To me, your post is joke.

Mikrotik''s suggested way of upgrading ROS on devices is to execute ROS-builtin package updater. And this way works just fine. Sure there are other ways of doing it (dropping manually selected package files to device, netinstall), but whrn those ways are used, proper package file selection is entirely on the admin doing it.

Yes, I agree that lack of information about wireless driver package split in releases beyond 7.13 is disturbing. But OTOH Mikrotik's official statement since forever is that change log only contains changes since previous version and that anyone interested should read all changelogs of any interim releases (and man, when doing upgrades between major versions and even manually, you definitely should be interested). This was true even in v6, e.g. when upgrading from 6.47.1 to 6.49.17 ... while at this, it was even uglier if one was sticking to long-term channel where change from one minor version to another - e.g. from 6.47.x to 6.48.y - only brought changelog between latest releases in new minor version - e.g. 6.48.y-1 and 6.48.y ... even though logically speaking (from version sequence within same release chain) those were sequentual releases. In v7 there is no long-term version (yet) to begin with and using any other release chain is somehow risky and calls for admin's attention anyway.

To be fair the fact that a given (wrong) practice has been in effect in v6 doesn't justify in any way insisting on it in v7.

In other fields, when *something* results in a given number of (minor) accidents or a single serious one, that *something* is usually changed (hopefully for the better).

The fact that traditionally very relevant info such as the packages needed for a given device is on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard., is not a good reason to not move that info in a more visible place.

Judging from the number of posts by people that have this issue with missing wireless drivers (and considering that there must be an unknown number of people that before posting search for the issue and finds one of the n related threads and thus do not post) this specific one is very, very common.

Why the good Mikrotik guys like to potentially alienate a number of their customers over the lack of a copy-paste on each post 7.12.x release docs a single sentence *like*:
Warning: starting from 7.13 the wireless package is not anymore in the main RoS and needs to be installed separately (from the extra package) for the devices requiring them <link to a page listing the models that need the wireless package>
remains a mystery (to me).

Why the good Mikrotik guys like to potentially alienate a number of their customers over the lack of a copy-paste on each post 7.12.x release docs a single sentence *like*:

Yes. But until when? For me this is already obsolete news, all of my devices, which deserve running v7, are already past 7.13. OTOH there will be people trying to upgrade their gear from anything pre-7.13 to (then current) v7 ... in years to come. And this issue will always only hit those who don't follow the most covenient path (use of built-in updater ... I'm avoiding to use term official here as other ways are officially there as well) ... which does either force one to search internet for the way forward (upgrade ftom v6 to v7) or will handle the "discontinuity in wireless driver handling" gracefully (upgrading via 7.12.1).

The only "sustainable" way of handling this (and other similar) issue would be intelligent merging if changelogs ... meaning changelog would list all items between some older and some newer version. This way, the warning about wireless package split woukd ge shown to everybody upgrading from pre-7.13 to post-7.12.1, but not to those upgrading from one post-7.12.1 to another post-7.12.1 version. This could work even for downgrades (listing fixes and features that will get lost due to downgrade).
Sadly MT didn't accept this idea so far (possibly due to the way they currently manage the tracking of changes).

BUT: even this would only work if person, trying to upgrade without using ROS-built-in updater, bothered to actually check the changelog. I wouldn't be surprised, if @OP failed to do so ... based on his 10-year experience of doing things in his own way.