Windows 10: "winsat formal" fixes slow disk problem temporarily

The question is in the bottom.

I bought my laptop 6 months ago and installed Windows 10. Everything was fine after the installation but after installing the drivers and windows updates windows became awfully slow, lagging every so often, disk 100% almost all the time and it takes MINUTES to just open start.

I have been looking for a solution or a reason for this for a while and tried a lot of things but nothing worked. Yesterday i saw someone on reddit suggesting to run the "winsat formal" command, when i tried it, it worked and solved the problem. But every time i restart the laptop the 'speed' effect is gone and i have to run that command again.

So the question is, what exactly did the command "winsat formal" do to my laptop? Also is there any harm in running the command every time i launch windows?

submitted by /u/Mobot29
[link] [comments]

:)

 

Winsat formal crashing


Try downloading and running the (portable) Winaero WEI Tool. It seems to work when Winsat does not. Why? Who knows?: Downloads / Software / Winaero WEI Tool





Good luck,

 

Winsat formal crashing


Those must be some of most useless benchmarks ever. That's just a front end for what Windows do during installation to very roughly determine some initial user settings, Like performance settings.
Look at this:



Newest processor with 6/12 cores @4.1GHz gives it 8.9 and very basic, low end GPU gets 8.2 and 9.9. Score for SSD is almost same as for a HDD. I was getting almost same score for a dual core Athlon, 512 MB Gpu and HDD.

 

winsat formal failed in windows 10

Hello Harkanwar,

Thanks for your reply and clarifying which queries are resolved in this forum.

Fair enough. I wish someone did find a solution for windows 8.1 "winsat d3d -dx10" dx10 test which is skipped. Most likely it is a winsat incompatibility when testing drivers with wddm 1.2 legacy support. This is what should be investigated. I do have intel
hd 3000 with latest 4229 (last four digits) driver. Same driver worked flawlessly under windows 8.0 and winsat d3d test. All hardware are recognised and working fine. Tested with passmark performance test and direct3d dx10 in windows 8.1 have same result with
windows 8.0. However 2D graphics mark was much lower compared to windows 8.0. Probably it has to do with windows 8.1 and wddm 1.2 legacy support or directX 11.2 windows support vs directX 10.1 hardware support (intel hd 3000).

The question is how did Microsoft produce/signed a windows 8.1 certified driver for intel hd 3000, that skips d3d dx10 winsat test. It is something that they have to fix asap, both microsft and intel (or is it a winsat bug???).

Just for the record I have posted same question with winsat.log in Lenovo forum, Intel forum, and here. Hope that there is a good Samaritan from Microsoft that will investigate this matter further.

PNP Device ID PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09\3&21436425&0&10

Cheers