back here: now that everything is square, I can't get get insider preview builds because "safety parameters" that MS considers wrong and ask me to rebooot for correction, rebooted twice, still the same stupid message ! what's wrong now ?
Most likely, your problems earlier resulted in some files being lost that Windows needs--probably an in-place upgrade install of the build will correct that. Hopefully, you have a repair disk made for the build you are using. Study up on Windows repair tools (that come standard with Windows) and learn how to "fix mbr" (unless you are UEFI) and other steps. Sometimes with a boot problem it is as simple as booting up your repair DVD and selecting "fix boot problems relating to startup" (or something like that) and the automatic routines can repair the drive--then reboot and you are back in business. It just pays to learn your way around those repair options.
I can't see an boot problem would inpact getting previews ? ran scannow, one extract: 2016-04-30 20:49:02, Info CSI 00004f9a [DIRSD OWNER WARNING] Directory [l:67 ml:68]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework" is not owned but specifies SDDL in component Microsoft-Windows-WWFCoreComp, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2016-04-30 20:49:02, Info CSI 00004f9b [DIRSD OWNER WARNING] Directory [l:59 ml:60]"\??\C:\Windows\Inf\Windows Workflow Foundation 3.0.0.0\0000" is not owned but specifies SDDL in component Microsoft-Windows-WWFCoreComp, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2016-04-30 20:49:02, Info CSI 00004f9c [DIRSD OWNER WARNING] Directory [l:57 ml:58]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft" is not owned but specifies SDDL in component Microsoft-Windows-WWFCoreComp, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2016-04-30 20:49:02, Info CSI 00004f9d [DIRSD OWNER WARNING] Directory [l:72 ml:73]"\??\C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0" is not owned but specifies SDDL in component Microsoft-Windows-WWFCoreComp, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2016-04-30 20:49:02, Info CSI 00004f9e [DIRSD OWNER WARNING] Directory [l:47 ml:48]"\??\C:\Program Files (x86)\Reference Assemblies" is not owned but specifies SDDL in component Microsoft-Windows-WWFCoreComp, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} is this a clue ?
Surely different worlds, and a son isn't surely comparable with a PC, but a good IT technician IS comparable with a good doctor, their job is exactly the same just applied to different areas. Anyway I'm not looking for pointless deabates, just exposed my POV
Check your event log to see what chhkdsk did (assuming you used the /R switch as I suggested), how many defective sectors were found (if any) and so on. If your drive is still in good conditions I would just do an in place upgrade (install windows on top of itself, keeping everything). If your drive had a lot of defective sectors, just stop to do anything, get new drive and clone there your old one, then do an in place upgrade.
If you're in the mood to try something else 1. Reboot 2. Run these 2 commands, one after the other, on an admin command prompt, then reboot... Dism /online /cleanup-image /scanhealth Dism /online /cleanup-image /restorehealth 3. Run on an admin command prompt, then reboot... sfc /scannow 4. Test the pc... Hope this helps you
That's a good way too, but in my experience the inplace upgrade is way faster, and almost always requires no manual intervention during the process On the other hand the sfc / dism thing is slower but the PC remain usable during the process, so chosing a way or another depends on the user situation and the local hour. (if one is going to sleep, launching the inplace upgrade is surely better, the next day the PC will be, hopefully, up and running)
Might want check see ACHI is enable?? Also, May have older drivers??? Also, check the Fimware on Computer?
Frankly is hard to believe that two different commands can check every OS file in two minutes, even on a top notch machine.
I expected you reply as well, but even if you spent all of your money to buy a superfast PC, the opening poster likely does not. So the suggestions to be useful must take that in account, better to show how poerfull is your setup on a thread dedicated to that matter.
Don't talk bull**** You're trying to make me look like a show-off... Read what you wrote... Now take it up the a** since it's clear you're not man enough to admit guilt
as no non-destructive solution worked, I made a clean install after having formatted C:\ thank you all
Yeah yeah, I know is major pita this solution but it's faster compared to the time you spent investigating and dissecting your malfunctioning system trying to find the specific cause. This is what I've been talking about since my first post on this thread.
Clean install is not format. With a clean Install you don't have to backup anything, as your data will be moved to windows.old and would easy to recover, as are easy to recover the settings of many programs, like browsers, downloaders and so on. NEVER format, unless you have a really really messed up filesystem, it's a pointless waste of time.
If you'd mention in your OP that you use an SSD, I had NOT given the advice I posted! I simply was thinking you used a 'normal' HDD! It would be all times better to post also the Hardware used and/or affected! That applies for driver's too!
I see I used the wrong terms as I formatted the drive at the begiining of the install process before starting the installation itself, luckyly I saved all valuable contents a few days before on the non system HDD.