"Good news", but we all, who uses Windows 10, know this and huge more problems with this Windows 10 version already about month and +. More - even Microsoft developers know, but they haven't did nothing. At least nothing haven't still changed, knowbody haven't said nothing about repaired release or upcoming updates. So if cannot use this version, should go back to previously known working version. Till now it is the only working solution. PS The next version should contain much more horror, at least they promised.
Does anyone know if the October updated ISO 1809 version (fall update) have been released in MSDN? If yes could a subscriber post a photo with the hashes of the En-US ISO? Thanks!
1809 (17763.XX) has not yet been released from the Insider Program. It is still in the Slow Ring & Release Preview Ring. So no updated ISO's.
That's strange, all the media covering Microsoft talked about the "zip bug" and, in this thread, was also talked about that topic several times. https://forums.mydigitallife.net/th...ld-17763-1-pc-rs5.77945/page-128#post-1474914 https://forums.mydigitallife.net/th...ld-17763-1-pc-rs5.77945/page-129#post-1475098 https://forums.mydigitallife.net/th...ld-17763-1-pc-rs5.77945/page-134#post-1475700
On the flip side, the stringent limits imposed on equipment regarding EMI (electro-magnetic interference) have resulted in manufacturers putting bigger and bigger decoupling capacitors across the power lines and to the earthing pin. This increases power consumption, messes with the power factor, but most importantly, poses a safety hazard. The earthing pin is usually connected to the equipment chassis. If the wiring is faulty and there is no ground connection - i.e. the earthing pin is left floating (this happens more often than you'd expect, especially in third world countries) - the decoupling capacitors create a potential divider causing the entire chassis to sit at half the ac mains voltage. This isn't too bad in the US with 115V ac mains, but in other parts of the world where you get 230V ac, this is quite nasty.
I wouldn't count on it, not with a major outstanding bug. But it's Microsoft, so there is no answer or educated guess on the actual release date.