Closed sipsuru closed 1 month ago
It looks like the user didn't replace the file correctly.
It's patched by automated patching !?
But seems like device specific though. No work needed. 😊
QUIZ: Is there any paticular reason for removing fiddler.dll
and hostpolicy.dll
from Yukihana-Patch 1.1.1
?
[ Well, the automated patching can't automatically select a version for patching now. I'd to manually set 1.1.0
instead of continuous
. 😕]
QUIZ: Is there any paticular reason for removing
fiddler.dll
andhostpolicy.dll
fromYukihana-Patch 1.1.1
?[ Well, they automated patching can't automatically select a version for patching now. I'd to manually set
1.1.0
instead ofcontinuous
. 😕]
emmm....maybe, it is bug😂
Some reported that the
server
is not up after patching correctly. I couldn't figure out the actual reasons.Milestone: https://github.com/sipsuru/fiddler-everywhere-patch-automated/milestone/1
There's no way that the error[s] are caused by incorrect patching, (as patched by automated-patcher).
Could something (IDK but something like a dependancy that require specific / additional permissions or something like that) from
server
cause this error inspecific
systems or environments ?Or is it a given that the error must be related to the system not
server
. (I too think this could not be related to theserver
though.) ?