https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15208
Guy Harris <g...@alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
OS|Windows 10 |All
Hardware|x86-64 |All
Status|IN_PROGRESS |RESOLVED
--- Comment #11 from Guy Harris <g...@alum.mit.edu> ---
This should fix it.
To test it, you'll have to wait for an automated build with the fix to show up
in
https://www.wireshark.org/download/automated/win32/
for 32-bit Windows builds and
https://www.wireshark.org/download/automated/win64/
for 64-bit Windows builds. Mac users should look in
https://www.wireshark.org/download/automated/osx/
Look for "2.6.5rc0" builds if you want a 2.6.x build, "2.4.11rc0" builds if you
want a 2.4.x build.
Note that installing such a build may, or may not, allow Windows auto-updating
to work when 2.6.5 or 2.4.11 are released.
Note also that they're "bleeding edge" builds and may have more bugs than you'd
like.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
