Disable Could not reconnect all network drives Notification in Windows

AlainCh2 · 21 Jan 2021

Hello Brink,

I keep getting this error, so I suppose that's not the correct tutorial.

Am I right?

Disable Could not reconnect all network drives Notification in Windows-image.png

My issue is:
I have a twin system (White & Black) and I share their disks
so they are to be accessible from the other one when it is waken up.

Usually I fire up only one, and work on that one only, so I get the annoying error.
Sometime I need both and so I don't care if the error appear on one or the other.

The idea is not to have a list of Warnings ...
....missing reconnection.... at startup,

when I know perfectly why !!!

Thanks

Alain

Brink · 21 Jan 2021

Hello Alain,

That does indeed look like a separate issue than what this tutorial covers.

As a test, remove the network connection, and set it up again with a different drive letter than "A" or "B" since those are usually reserved for floppy drives.

AlainCh2 · 22 Jan 2021

Thanks for the answer Brink.

If I dont have B: to show up an error it will be the first next:
T: T3 Megadisk

Strange as it can be,
I have no clue where to find the root of these messages

Alain

Brink · 22 Jan 2021

AlainCh2 said:

Thanks for the answer Brink.

If I dont have B: to show up an error it will be the first next:
T: T3 Megadisk

Strange as it can be,
I have no clue where to find the root of these messages

Alain

Just to verify, is it still giving you this issue?

AlainCh2 · 22 Jan 2021

hmmm, yes
When I start ONE computer it complain about not finding the other :-D
(but not when I WOL them simultaneously)

Why do you ask?

PS: it's not an issue, for sure.
Just a very annoying message I would get rid of

Brink · 22 Jan 2021

AlainCh2 said:

hmmm, yes
When I start ONE computer it complain about not finding the other :-D
(but not when I WOL them simultaneously)

Why do you ask?

PS: it's not an issue, for sure.
Just a very annoying message I would get rid of

I'm not sure it can be solved permanently unless using something like a NAS drive connected to a router for the computer to access instead.

AlainCh2 · 22 Jan 2021

Brink said:

I'm not sure it can be solved permanently unless using something like a NAS drive connected to a router for the computer to access instead.

I have a pseudo Nas on the internal router.

That drive don't give instant error, even disconnected,
unless I try to access it.

That's the big difference ..
... you get the error even not using it,
if it's in the other PC.

- - - Updated - - -

Good news

I restarted the Black PC several time today, to dissect the reason it was not accepting WOL,
as it was doing yesterday.

Last three reboots the message has disappeared, no reason given.
I didnt change registry, nor any other connected item for what I know.

I was dealing with checking BIOS and device manager settings.
> where I discovered W10 was rolling back my setting
>re-enabling "authorize computer to sleep this device"

Before putting myself on WOL issue,
I was thinking to accept your suggestion to move out the B: letter for the download directory,
but that error _NOW_ don't even seems related to that.

If I discover something I report back.

Thanks again

Alain

syntoh · 25 Jan 2021

Entering this reg settings presented in this tutorial really disables the Message.
But it also disables the "Reconnect at sign in" setting.
After this reg entry is set, the Mapped drives are crossed out red after logon.
This is why the message don't show up again.

syntoh

AlainCh2 · 25 Jan 2021

syntoh said:

This is why the message don't show up again.
syntoh

No sure of that. (I had doubts myself)
because it took 48 hours and maybe 20 boots to kick in ^^^

But I confirm the message don't reappear anymore after boot

(just another strange thing into W10)