![]() So anyone that had previously set their proxy setting to Direct connection if they didn't do a clean install of 5.1.889 (and possibly 5.1.864 or PR builds) could well fall foul of this apparent problem with the Direct connection option. Unfortunately after the beta testing I did a clean reinstall on my XP Pro system and that is set to Auto detect, so I didn't notice any problem in 5.1.864 nor when I did a program update from the UI to the 5.1.889 build as it was still set to the default Auto detect.Ī quick test changing to Direct connection (no proxy) resulted in the error, see image, I don't know what file it can't find as that would seem unrelated to the proxy settings as it doesn't even seem to get that far. I did the beta testing on my XP Pro system and that was set to direct connection and the updates worked right up to 5.1.863 (just before 5.1.964). ![]() I'm on XP Pro and on win7 starter (clean install of 5.1.864 and UI update to 5.1.889) and both work. I think it somewhat strange if it worked with 5.1.884 I would have though it would work with 5.1.889.
0 Comments
Leave a Reply. |