New
#40
I turned it back on, but only for the LAN. No way am I getting into Internet peering for the purpose of sending or receiving updates. Zounds!
--Ed--
Am I the only one who feels that issuing a new build with glaring bugs like "personalisation menu may crash" (which it does on my pc) is not acceptable?
I just feel that a new build should fundamentally be as functional as previous build before it is released. New changes should not break things like seems to be happening just a bit too frequently. For crying out loud - it was the power button last time. How could anybody miss that!
I fully accept some obscure interaction bugs with existing features may creep in, and NEW features may be buggy (if you do not accept that , you should not be on Fast Ring) but previously working features such as bash and personalisation blatantly not working - come on!
This really smacks of poor QA by MS and, frankly, makes them look incompetent and amateurish.
I am certainly going to feedback that to MS - they really need to get their act together in my opinion.
I agree with that entirely cereberus. I came off the Fast Ring a couple of months ago for two reasons.
First, I am only running one PC now (donated my second machine to a needy relative)
Second, Microsoft are getting sloppy in the Fast Ring releases. Yes you expect to see bugs but not ones as major as Fast Ring are seeing now. Seems to me the Fast Ring is being treated as Microsoft employees who like working for nothing.
Talking of problems. anyone else have network discovery problems?
all down
all done..
- back to Fallout4
- new gfx hardware arrives tomorrow..
- most excellent!
It MS wants to speed up WU build downloads just let them upload the image to Torrent Servers :)
Of course I turn this off unbelievably insecure method of updating. I suspect MS just is hoping to reduce the load on its own update servers.