W
WebMaximus
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!
Here's a couple of screenshots showing the issue. The first one, you can see these weird looking paths highlighted. Above and below, the paths look normal as you can see. The paths beginning with F:\ are left since before the disk was cloned. These are the same as the paths now starting with D:0\ after the disk was cloned.
The second screenshot shows what things look like in Windows Disk Management. As seen, it looks perfectly fine there and the partition in question is assigned the drive letter F. Just like it should be and was before the clone. So I really don't understand why Window Firewall is now referring to programs on the F partition using a path starting with D:0\ rather than F:\
Continue reading...
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!
Here's a couple of screenshots showing the issue. The first one, you can see these weird looking paths highlighted. Above and below, the paths look normal as you can see. The paths beginning with F:\ are left since before the disk was cloned. These are the same as the paths now starting with D:0\ after the disk was cloned.
The second screenshot shows what things look like in Windows Disk Management. As seen, it looks perfectly fine there and the partition in question is assigned the drive letter F. Just like it should be and was before the clone. So I really don't understand why Window Firewall is now referring to programs on the F partition using a path starting with D:0\ rather than F:\
Continue reading...