Reply to thread

Message: <blockquote data-quote="orbs80" data-source="post: 141739" data-attributes="member: 11792">That's pretty pants <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" />MS have passed all the information on to HQ anyway so I guess it'll be fixed in the first service pack <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />Basically, they don't know what is causing it and have no real answers, although disabling the HomeGroup Provider worked for me it isn't working for you. Most odd.Also doing a cross comparison with Windows 7 Networking and Windows 8 there is not much difference on the surface apart from the way the HomeGroup works and the fact you can no longer switch between Public, Home and Work Network scenarios.You'd think they would have at least have been able to tell you what processes/services are used to automatically populate the Network section in File Explorer. I hate the way they are not proactive with updates to fix issues and collate them for a later cumulative update or even wait for a service pack.</blockquote>