Re: TightVNC 2.8.8 on Updated Win10
fragmentux <[email protected]> Wed, 31 Jan 2018 19:40:29 +0000
| Newsgroups | gmane.network.tight-vnc.general |
|---|---|
| Message-ID | <[email protected]> |
Hi
thanks for your idea .. unfortunately, neither of those KB's have been
installed on my system. It seems my system does not qualify for them.
I did, however, take a look at what has been done
and found only 4 updates. They are, of course, the 4 big ones !
Rolling back the changes (for what it is actually worth .. )
o kb4049411 - After removal: no difference,
tightvnc crashes immediately.
o kb4033631 - After removal: partial resolution.
tightvnc crashes after a minute or so.
Note: Restarting service does not restore comms or the systray icon.
Rebooting shows no difference in behaviour.
(Rolling back the changes was not worth a dime .. )
o kb4049065 - *Cannot* be removed
tightvnc still crashes .....
Microsoft's relentless lies force me to conclude that they have no other
interests than there own greedy, money grabbing, non-competitive history
has proven to date.
I quote a Micro$oft lie right here:
"To uninstall an update, select it from the list (no really)
and click Uninstall or Change" (surely not .. ? )
Additional: "Or, if not .. then it *cannot* be removed :P"
The source code reads:
"# Screw them .. we decide who gets what not them."
But it is closed source so ..
o "Security" update for Flash Player
Not even going to bother with that.
I hope that the devs at tightvnc will have a look at the problem and a
solution can be found.
Regards
Frag
PS:
What I find really funny is this ..
For over 10 years not one single person had actually read the intel
manual, not until Jann Horn did .. and now look at the fkn mess ...
There are a lot of IT security "experts" out there who did not RTFM.
On 31/01/18 17:19, [email protected] wrote:
> Yes there is. There is a specific update causing communications failures
> which is KB4057144 (for Windows 8 systems it's KB4056895). You can uninstall
> that update and then block it from re-appearing with a windows utility.
>
> See this page:
> https://support.microsoft.com/en-au/help/4057144/windows-10-update-kb4057144
>
> and/or this page:
> https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/kb40
> 56891-is-blocking-my-vpn-connection/d849032e-a659-4f24-90d3-24c1fbda9d4c?tm=
> 1515536013715&auth=1
>
> Terry >
>
> -----Original Message-----
> From: fragmentux [mailto:[email protected]]
> Sent: Wednesday, January 31, 2018 8:38 AM
> To: [email protected]
> Subject: TightVNC 2.8.8 on Updated Win10
>
> Hi
>
> I used tightvnc 2.8.8 (server) on Windows 10 (pre anniversary update) and it
> worked flawlessly.
>
> I connect from a Linux desktop to a Windows 10 machine.
>
> This Win10 machine has been left OFF the Internet to avoid being updated.
> Unfortunately, unforeseen circumstances have now forced the update and there
> is nothing I can do about it.
>
> Since the Win10 is now fully up to date with Microsoft's disaster patches
> for Meltdown/Spectyre, tightVNC crashes after a seconds of use.
>
> I doubt there is much I can do except wait for an update for tightvnc.
>
> I am posting this message to ask if anybody else has seen similar problems
> with Windows 10 (upto date) and tightvnc 2.8.8
>
> Thanks for reading, regards
> Frag
>
> ----------------------------------------------------------------------------
> --
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> ___________________________________________________________
> TightVNC mailing list, [email protected]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list