Forum Home
Press F1
 
Thread ID: 140680 2015-11-25 20:19:00 Win10 network sharing bk T (215) Press F1
Post ID Timestamp Content User
1411939 2015-11-27 04:55:00 I did the check again, this time pointing to a known-to-be-good Win8 Pro iso, copied those details to google search but get the same result - did not match any documents! bk T (215)
1411940 2015-11-27 07:24:00 I get mine from www.microsoft.com Scroll down the page a little.

Theres several Versions, dont get the N or K.

Theres also English or English International. The Previous Hash was from Windows 10 + English x64

The English international Details:

Name: Win10_1511_EnglishInternational_x64.iso
Date: 25/11/2015
Size: 3 GB (3,989,231,616 bytes)
--------
SHA-1: 250f8ff043ceb395f95cee6120efc323f69e7f8d
MD5: 3c45cb361bf29098c2536e14a2be6f1c
CRC32: 770d6209

Before running the hash checker, esp if you have used it before, run Ccleaner to clean out all the temp/rubbish, I have found sometimes they will give false readings other wise. ( they will show in Red on the checker if its not correct)

If you google the SHA-1 above you'll see the results

Part of Googles results, from this site www.thecollectionbook.info
6843

I personally look at the MSDN Download site, which gives the SHA-1 Codes. -- Its free to look, but you cant download anything unless you have a subscription.
6844
wainuitech (129)
1411941 2015-11-27 10:10:00 Downloaded the ISO from your link, hash check seems to be OK. Reinstalled, performed sfc scan produces same results:

"Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.log Windir\logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log.
Note that logging is currently not supported in offline servicing scenarios."

Haven't checked the network sharing yet, will do it tomorrow.
bk T (215)
1411942 2015-11-27 19:13:00 Have a look at the log bk and see what it indicates. The faults may be few in number and unrelated to anything you need to use.

I put the blame on WT :) if he had not suggested that we run sfc we would probably be happy with the install as it is.
CliveM (6007)
1411943 2015-11-27 20:20:00 Have a look at the log bk and see what it indicates . The faults may be few in number and unrelated to anything you need to use .

I put the blame on WT :) if he had not suggested that we run sfc we would probably be happy with the install as it is . Dont go blaming me or anyone else for that matter if a system check is run and it finds faults . Blame Microsoft for creating a fault riddled unstable system .

If sfc created problems then run system restore back to before it was run -- Easy eh :p
wainuitech (129)
1411944 2015-11-27 20:40:00 Microsoft really messes it up with Win10. Win8 was bad enough but it's no better this time! MS doesn't seem to learn their lessons. bk T (215)
1411945 2015-11-27 21:29:00 Microsoft really messes it up with Win10. Win8 was bad enough but it's no better this time! MS doesn't seem to learn their lessons. Yeah, I can see what they are wanting to do - Combine the one OS into every Windows device. Which in theory is so-so, but the tasks done on a tablet or phone are different to that of a PC.
Was speaking to a lady yesterday and she said the same thing, her phone is OK for doing basic stuff, but shes always going back to her laptop as its so much better.

What annoys me is EVERYTIME Microsoft seem to be keen on breaking networking -- What the hell they are upto is anyone's guess. If they think everyone's going to use Homegroup - Bad news for them, not going to happen. Homegroup is shaky at the best of times.

Can understand if the previews and testing versions have bugs, BUT they should be sorted BEFORE releasing to the general public as updates. Maybe by 29th July 2016, when its no longer free it "may" be a little more stable. ;)

ANYHOW--- Hows the networking going BK ? is it still causing problems ?

If it is, just a long shot / test, try giving the Computers a static IP address, just in case theres something weird going on with this latest build and your Router.
wainuitech (129)
1411946 2015-11-28 01:09:00 Win10 is showing up my other 2 Win7 machines (both connected thru wireless -same router, of course) but not my Win8.1 PC. They are all sharing very happily but Win10 doesn't like to 'see' me (Win8.1 - my main PC); I could 'see' and access its shared folder, though. bk T (215)
1411947 2015-11-28 02:08:00 Put teamviewer on the ones that dont work if you want. I'll check it out for you Speedy Gonzales (78)
1411948 2015-11-28 02:29:00 Win10 is showing up my other 2 Win7 machines (both connected thru wireless -same router, of course) but not my Win8.1 PC. They are all sharing very happily but Win10 doesn't like to 'see' me (Win8.1 - my main PC); I could 'see' and access its shared folder, though. Just a thought -- They do have different network names dont they ? Cant have two with the same name. wainuitech (129)
1 2 3 4