Windows Firewall and odd looking paths showing D:0\ instead of drive letter

W

WebMaximus

Contributor
Joined
Sep 26, 2018
Posts
32
A couple of days ago, I replaced my SSD with a bigger one. On the disk, I had two partitions - one 100 GB for Windows (C:) and one 400 GB for other stuff (F:). To replace the disk, I used a tool called AOMEI Backupper which comes with a disk cloning feature.

The cloning completed successfully without any issues, the computer started normally and everything seemed to be OK. Then, I noticed one strange thing when I was asked to allow applications through the Windows Firewall. Applications I already allowed long time ago. When looking closer, I realized why I was asked again to allow them though the firewall. For whatever reason, the path to applications on the F: partition after the cloning is D:0\ rather than F:\

I only see this in the Windows Firewall. I've checked in Windows Explorer, Disk Management, Diskpart and all looks OK and normal in all those places. It's just when looking at the Windows Firewall rules I see this odd syntax for the path. And only for applications on the F: partition.

Any advice how to force Windows Firewall to use the normal syntax again would be highly appreciated!
 
My experience is that MS and AOMEI may each pass the blame to the other party so hopefully someone who has experienced a similar problem will spot one of your threads and post a solution. My guess is that Windows Firewall is using some registry key which has not updated correctly during the transfer. Searching in Registry editor for D:\0 may help you track it down.
 
That's good thinking and great advice but sorry to say I already tried that thinking the same.

Was surprised to not find a single D:0\ in the Registry. So this seems to go even deeper into the core of Windows and its disk management.

What surprised me even more was how deleting the partition/volume and then recreating it using Windows own Disk Management tool still didn't fix the issue.
 
Actually, what I said in my post just above wasn't fully true when I said I didn't get a single hit searching the Registry for D:0\.

I did get a number of hits, but they were only for the firewall rules showing the same thing I see in the Window Firewall UI. If I manually remove the rules with D:0\ in their paths, I do get zero hits searching the Registry.
 
If you create a new rule, the path will be changed from f:\ to d:0\ ?

If the firewall creates the correct rule, do you need to change the old rules only?
 
xilolee said:
If you create a new rule, the path will be changed from f:\ to d:0\ ?

If the firewall creates the correct rule, do you need to change the old rules only?
Click to expand...

Yes, whenever I add a rule for an application on the partition with the letter F assigned to it, the path in Windows Firewall will show D:0\<path to application> rather than F:\<path to application>. I've also seen the path for one of the applications show D:1\<path to application>. This application is a bit special though. It's located on the other partition of this disk (C:) which strangely enough won't give these odd looking paths for other applications found on C: but only for this particular application. The application is the beta version of the upcoming MS Flight Simulator. Not sure why this is for only this specific application. All other applications on the C: drive will have normal looking paths in the Window Firewall.

To answer your second question. The rules created do work just fine. It's just weird why the paths look so strange and why the Window Firewall uses this syntax rather than the normal one like F:\... och C:\... rather than D:0\... and D:1\...
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top