Dear Kalpana,
Just google "windows 10 G3258 problem". Google is picking up on this, why isn't Microsoft? Please pay some attention. It's isn't so hard to piece together what's happening
Refering to generic Microsoft articles isn't adressing the real problem. Somehow after build 10130 code was introduced that's seems to effect systems based on an Intel G3258 processor. From the different posts it seems the chipset (H81 or Z97) doesn't really
matter. The processor seems key.
Simply boot any G3258 based system (with all cores enabled) and windows 10 won't boot after build 10130 (10240, 10168 etc). Upgrades from any build (10130 or less) from to 10168/10240 will fail with 0xC1900101 - 0x20017 error or a boot loop. Any attempt of
a clean clean system install and/or boot from 10168/10240 installation media (DVD / USB) will result in a boot loop. Believe me I've tried everything and so have others with the same results.
The only confirmed "workarround" so far is disabling a processor core in the BIOS. Effectively turning the G3258 into a single core processor. Once you do that all other options suddenly work: upgrade via windows update, upgrade via DVD/USB, clean install from
DVD/USB. This workaround will allow you to update windows 10 to build TH1 10240 via any of the usual means. However once you are on 10240 and try to enable all processor cores again you are back at a boot loop.
Unless Microsoft wakes up and fixes this bug any G3258 system will not be able to upgrade to windows 10 as the majority of system owners won't even begin to grasp howto disable a core in the BIOS (if they even now what a BIOS is)
Apodictus