delsoo, ah just realized that yours is sl edition. wrong checksum then. will try find the matching one later.

The command is fciv -md5 your.windows.10.iso

replace your.windows.10.iso with correct iso file name with extension.

btw that's the wrong way to create a bootable usb stick. first find out whether your w10 is in uefi mode or bios mode. In control panel > administrative tools > run system information.

Nice tqvm!

Yes.

What's so complicated? I thought of guiding you through a simple process of creating bootable usb stick manually, because i suspect that your iso file is good after all. It didn't work because you did it wrongly apparently.

Nevermind just do what you want. The media creation tool is the same anyway hehe

since you said it's uefi then try this:

1. copy the iso file from usb stick to your hard drive. if you have a copy in your hard drive skip this;
2. format your usb stick with fat32;
3. open your iso file with winrar, then extract its contents directly into usb stick. there is no need to select anything in the iso, use extract button and point the destination to your usb stick and continue.
4. if you wanna do upgrade, run setup.exe in the usb stick; if you wanna do clean install, on reboot, hit the key that let you select boot device and choose uefi: <usb.stick>

edit: step 2 and 3 is how you create bootable usb stick for uefi install manually.

for bios mode install, do step 2 as formatting usb stick with ntfs. step 3 is the same. depending on your system bios, you may need to set your usb stick as active to make it work (using diskpart). alternatively, use rufus.

This post has been edited by horns: Jan 13 2016, 12:14 AM

ok. are you running with w10 on ssd or hdd?

oh ok. well nevermind.

it's fine to do it on w8. w8.1 is much better.

never happen to my computers. it's weird that you have formatted your drive but there was still a windows.old folder in c:.

is this an upgrade or clean install?

thanks a lot!

yeah it's not a good idea for ms to include drivers in windows updates. however automatic driver updates can be disabled. press win+x keys, select system, goto advanced system settings > hardware tab > device installation settings.

the person who told you that one of the values is about turbo boost must be a joker, because both of them are base clocks (intended vs. current base clock)

the solution is to use third party tools like hwinfo to display system information (also in more details).

edit: this is the official way from MS to disable GWX nagging screen, https://support.microsoft.com/en-us/kb/3080351

This post has been edited by horns: Jan 15 2016, 01:37 PM

Thanks a lot! Saved for collection purposes.

From the changelog i will skip testing this one also. The current stable 1511 is good

http://windows.microsoft.com/en-us/windows...rror-0x8007000d

nice

the hardware acceleration thing in chrome? try turn it off and see if it solved the issue.

UPDATED ESD DECRYPTER FOR BUILD 9926-14251

http://rghost.net/6Xf7xxPYn

yes.

basically a 32bit os cannot be upgraded to a 64bit w10 directly. however, once you have upgraded to w10 32bit from the old one (make sure the computer is online and activated), and you do a clean install to get rid of the 32bit os and replace it with a 64bit w10, you computer should be activated online automatically.

about step 6, you extract contents of the iso file directly into usb drive, or burn the iso into dvd. some users did it wrongly by copying the whole iso as is into the drive, which will not work.

No. I mean you download and save the iso file in your hdd/storage with media tool, then make the usb/dvd installer with that iso.

it depends.

yes you can use tools like wudt or rufus for this, but there is an easier way if your mobo bios supports uefi. the process of creating a w8.x/w10 usb installer is as simple as:
1. format the usb stick with fat32;
2. open the iso file with archiving tools like 7zip or winrar, then extract the contents of iso directly into the usb stick.

it's a common problem (related to permissions). do a search with the error codes will get you options to fix it. the most probable fix is to run the tool with a local administrator account.

thanks a lot!

do you mind sharing more information like your pc specs, and more clues for others to help you better?

log entries in event viewer will be helpful. also, you can check out nirsoft's bluescreenview to check if there are logs created about such bsod's.

Yes, you should be able to do that.

I never experience bsods yet. There were some during old
tech preview days, but mostly were related to the unpolished state w10 was, and drivers at that point of time. (All fixed now) Since the initial july release iinm it's been solid. After 1511 it's even better.

ram-related? try reseat your ram, then run memtest86+ (http://www.memtest.org/) for at least 3 passes. (the test is lengthy; leave the computer on let it run while you sleep)

Maybe you should check out kaspersky's product helps/howtos about this.

No harm to run it again to make sure. Hardware issues must be rectified first. If it's the culprit, whatever software-based remedies will end up the same unresolved outcomes.

Another possibility is the intel gpu driver. You can try to get and use the latest one from intel download center.

the easiest one is to create a bootable usb stick with its usb installer. boot the computer with it and tests will be run automatically iinm.