Is this nrf52840DK really bricked?

Question

Hei! 
 Mid code development my ability to flash new versions went away. The only clue I have is that W11 installed some new drivers, but I'm grasping at straws. I have screwed up TWO dev kits over the past three days trying to figure this out. 
 DK#1 
 Can anyone explain why nRFConnect (v3.10.0) for Desktop, using Programmer (v2.3.3) under Win11 recognises my nRF52832DK as a JLink device, but then says it can't talk to it because it isays it s NOT a JLink or Nordic device? (see image attached) It worked fine initially and I successfully developed code for it for a while, but suddenly it just stopped cooperating. Obviously this is operator error, but after reading through all the stuff I can find, I'm flumoxed. 
 
 I have button+power-cycled + dragged and dropped "3566.J-Link OB-SAM3U128-V2-NordicSemi 160315" onto it when it shows up as a drive D:. 
 Zadig is in the equation too some time ago I recall. Could that be the prob. somehow? 
 I assume this has something to do with the fact that when I plug it in, the device manager reports like in this image below. 
 
 I have now compromised a DH#2 
 They both boot, but show different stuff in the D: drive.

Usually when I describe my problem I suddenly realize the real problem and the solution. This time I can see the problem, but not the solution. 
 Please throw me a line shipmates. 
 Takk 
 //Mik

Michael Lamming · Answer

Hi J&oslash;rgen , 
 After a struggle, yes I did manage to get things working under W10. Under W11... not so much. 
 History: I needed to demonstrate the Arduino IDE. As you know, the Arduino IDE is not officially supported by Nordic. But there is a well-described procedure for using the nRF52 family with Arduino that I referenced in my previous post. It involves a simple USB driver/library replacement process using a tool called Zadig. This has worked well for me under Windows 10. Moreover, it was fairly easy to roll it back for 'normal' development under SES or similar using the W10 Device Manager. 
 Unfortunately, under W11 I just could not figure out how to roll back the driver to the standard one, and get nRFConnect, or nrfjprog to find the nRF device. In the end I found the line-of-least-resistance was to remove a bunch of Windows Driver Packages installed by Segger and Nordic installs, and all programs that mentioned Segger, and Nordic . Then I reinstalled from scratch with a few reboots of course. 
 For the record, my "Zadig undo fix" for W11was as follows:

pnputil -d <every driver that mentioned Arduino, Segger, Nordic, or libusb>

Use Windows Apps & Features manager to remove all driver packages that mention SEGGER

re-install jlink software

nrfjprog --recover //Yay, it appears to work

re-install nrfconnect desktop app to see if it works - it finds a device called nRF52 DK

I don't know how many of the above steps are necessary, but this recipe worked for me. Guru's will hopefully be able to explain a more streamlined process, but I'm a mere mortal. 
 Cheers, 
 Mik