KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider
-
Average fragment per file 1.28. That is pretty much nothing. :)
MFT records is 773375. That is equally so nothing to worry about. :)
I just used Samsung Magician to Optimize my drive and get the same results. Seems that I can do without this app.
-
-
I just used Samsung Magician to Optimize my drive and get the same results. Seems that I can do without this app.
Just tried Magician. It says my Samsung SSD is not supported. Probably why it wasn't installed in the first place.
-
And after a reboot, I'm back in business.
-
-
-
Thanks! I've actually got the whole Sysinternals tool set downloaded. Every now and then I go and update them. Very useful tools. Mark R. is a wizard when it comes to these kinds of things. :)
-
Thanks! I've actually got the whole Sysinternals tool set downloaded. Every now and then I go and update them. Very useful tools. Mark R. is a wizard when it comes to these kinds of things. :)
They (MS) acquired him way back , and keep him hidden!
Mark Eugene Russinovich is CTO of Microsoft Azure. He was a cofounder of software producers Winternals before it was acquired by Microsoft in 2006.
-
They (MS)
acquired him way back , and keep him hidden!
Mark Eugene Russinovich is CTO of Microsoft Azure. He was a cofounder of software producers Winternals before it was acquired by Microsoft in 2006.
Yes, darn MS killed that project too, by sticking the wizard in the cloud.
-
I'm staying away from this build. The only thing this build has done is caused havoc on my asus rog laptop. It's crashed three times... one on a upgrade and twice on a clean install. I was stuck at the boot screen and then I would get the blue screen of death. It would crash on trying to get into safe mode as well. All my drivers were up to date. I never had any problems with windows 10 until this build. So I am waiting it out for a while.
***UPDATE*** Well I took the jump again and turned off all the VT-D stuff in my BIOS and had the same result. But this time I was able to get into save mode and got into MSCONFIG and turned off some services to see what was causing the issue. Nothing worked and had the same issue. The next time I rebooted into safe mode I did the "Disable Driver Signature" and my system booted right up on the next start up. From that point I knew it was a DRIVER ISSUE and it could be fixed. So it happens that Microsoft installed some junk Intel drivers that made my pc nonbootable. I installed Driver Booster and updated all my drivers and reinstalled my NVIDIA driver on my own and.....BOOM all working and I have done a few reboots to check and all is good. I even turned back on the VT-D stuff and all was still fine. So it was bad DRIVERS from Microsoft on the upgrade all along.
-
Hahhah, yes there has been a lot of Intel and nVidia driver issues going on lately. What I don't understand is why Windows can't revert to compatibility/limited drivers when it comes to any chip on the system. I mean if a GPU driver can't start, why not use a basic VESA driver. It would be bulletproof. Same goes for any hardware really, most has some form of compatibility layer that at least let you get your system up and running though slowly. But then it would at least be easy to fix any performance issues because of crippled drivers. Linux does this, why not Windows too?
Glad you got it sorted out. :)
-
-
Hahhah, yes there has been a lot of Intel and nVidia driver issues going on lately. What I don't understand is why Windows can't revert to compatibility/limited drivers when it comes to any chip on the system. I mean if a GPU driver can't start, why not use a basic VESA driver. It would be bulletproof. Same goes for any hardware really, most has some form of compatibility layer that at least let you get your system up and running though slowly. But then it would at least be easy to fix any performance issues because of crippled drivers. Linux does this, why not Windows too? Glad you got it sorted out. :)
I'm glad too bud believe me! lol I don't know why windows does this but I never had any issues like this on an upgrade before or in fact for a long time.