📎 AI Summary:
The thread discusses a recurring issue where Windows Firewall repeatedly prompts for app permissions at each reboot, displaying unusual file paths, particularly involving a drive labeled "B:0". The original poster clarifies that the paths are strange, and related programs like eMule are not installed, only portable versions, raising concerns about potential malware or corrupted entries. Contributors suggest checking for malware, reviewing system registry entries, and consider possible bugs or corruption with the paths, but the problem remains unresolved.
eXtremeDevil

eXtremeDevil

Banned
Joined
Feb 9, 2018
Messages
60
Thread Author #1
This happens every time I reboot. Windows Firewall asks me for letting an app through. I have granted the access before, but WF doesn't seem to remember. Also, the path is very strange:

An image from 'Windows Firewall keeps asking for permissions'. Windows Defender Firewall blocks emule.exe, asking to allow access on private networks only.


What may be happening? Thanks!
 

Last edited by a moderator:
Solution
eXtremeDevil
I figured it out. The HDD i was ussing for B drive was on SATA 0, so it was disk 0 on Windows, and C drive was disk 4 (yes, I have several HDD hehe). I changed the cables so now B is disk 4 and C is disk 0 and now it boots correctly, I mean, WF is no longer up, ESET takes the place.

What I fail to understand is the relation between firewalls and C not being the first physical disk, or maybe the problem was having a B drive on disk 0.

Is Windows that weird sometimes??
Sort by date Sort by votes
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
#41
That shouldn't really matter, Windows dynamically keeps track of the disks and the Letter assignment is simply a logical assignment and the letter to physical is maintained as symbolic links
 

Upvote 0 Downvote
eXtremeDevil

eXtremeDevil

Banned
Joined
Feb 9, 2018
Messages
60
Thread Author #42
That's what I'm taking about, what is wrong in there to mix up drives, satas and firewalls?? Because when I changed B to A the path was A:0\...
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
#43
That's because Windows would of updated the symlink. You can see them with WinObj from sysinternals.
 

Upvote 0 Downvote
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
#47
They will be under device harddisk# and GLOBAL?? you want to select File > Run As Administrator since some of the info won't show otherwise
 

Upvote 0 Downvote
eXtremeDevil

eXtremeDevil

Banned
Joined
Feb 9, 2018
Messages
60
Thread Author #48
I see, I will take a closer look. Any way of manually refresh those links? So it doesn't happen again?
 

Upvote 0 Downvote
You must log in or register to reply here.