have you tried other drivers pisthai others might work, I changed a few drivers before this one worked on my pc
can someone confirm if the esd i downloaded for client pro 64 bit is correct? CRC32: 6C8639DD MD5: 0D7BE47C24B8D868903F01599497CFA2 SHA-1: 88491F9E975C676CD6E109FB741AC3882038481A after upgrading my build i got this esd on my "C:\RecoveryImage" but the hash are totally different. my winodws works fine but should i be worried?
And why do you think it's in the folder RecoveryImage? Extract the .esd file to an .iso, mount and look what you get!
Did anyone check system restore? Mine was off after upgrading last night to 10049! Also, some of the drivers (MS drivers) in the device manager are dated 2013 and 2014
The ESD for update is encrypted and comprised of four images is different from that you got from RecoveryImage folder which has been decrypted. [Encrypted ESD] image 1: Setup files except ISO\sources\boot.wim and install.wim/esd image 2: Image 1st of ISO\sources\boot.wim image 3: Image 2nd of ISO\sources\boot.wim image 4: ISO\sources\install.wim/esd [Decrypted install.esd in C:\RecoveryImage] image 1: Setup files except ISO\sources\boot.wim and install.wim/esd image 2: Image 1st of ISO\sources\boot.wim image 3: Image 2nd of ISO\sources\boot.wim image 4: ISO\sources\install.wim/esd
I tried a few DOS commands today didn't get any errors but the setting didn't change either. I'm wondering if this is something to do with Spartan I don't see what good it will do, but here you go.
Not sure if I want to install 10041 or 10049. Looks like more problems with 10049 exist. I don't seem to have properly working USB 3.0 on my PC, so maybe 10049 has better USB 3.0 support considering they added 3.1 support? In other words maybe they worked on 10's USB support altogether?
Hello MDL members, After a wild and crazy day yesterday trying to install 10049, first from 8.1 then from 10041 which the attempts to upgrade from either versions of Windows failed, I then proceeded to the last resort. A clean install! And my problems with the mouse and possible drivers (a nod to ZaForD here) are GONE. I can now declare build 10049, in full with nothing missing-like the start menu-installed and apparently running well! Thank God! I will say one thing. This build installed FAST when clean installed. So I had to add 50 or 60 programs back in..it's worth the time to back up and do it the clean way!
@evergap, Do yourself a favour and do a complete backup. It is still a beta and is likely to go wrong, so that way you can restore back to where you are now quickly and easily.
ZaForD, A quick reply, I am doing a backup right now. I learned my lesson! Having some minor issue with Internet Explorer at the moment, maybe Emet related..but at least nothing at all like with 10041! Thanks!
Did you try this? Code: Would you like to configure DNS and WINS addresses from the Command Prompt? You can. See this example for DNS: netsh interface ip set dns "Local Area Connection" static 192.168.0.200 and this one for WINS: netsh interface ip set wins "Local Area Connection" static 192.168.0.200 Or, if you want, you can configure your NIC to dynamically obtain it's DNS settings: netsh interface ip set dns "Local Area Connection" dhcp BTW, if you want to set a primary and secondary DNS address, add index=1 and index=2 respectively to the lines of Netsh command.
Ughh its been almost 2 hours and its still at 22% Ffs M$ you should improve the upgrading process Next step going back to w8.1cause seriously every update its getting worse