Should "Defragment and Optimize Drives" be running for an SSD?

Page 8 of 9 FirstFirst ... 6789 LastLast

  1. Posts : 1,471
    Win10 Home x64 - 1809
       #71

    Thank you a ton - that is all I was really trying to accomplish and I thought it had something to do with what I was trying to do all this time.
    Hmm, guess I missed that part ... sorry about that. Thought is was just the IDE ATA/ATAPI Controller / Driver issue.

    I could of sworn I ran that Winsat before with no luck - what changed this time that I ran it?
    No clue, unless it was using the nForce Serial ATA Controllers and getting them under IDE ATA/ATAPI Controller vs Storage Controllers.

    I think you're good to go now, but check the following tutorial about trim if need be - Enable or Disable TRIM Support for Solid State Drives in Windows 10 | Windows 10 Tutorials

    Glad you got it sorted out tho and your welcome :)
      My Computers


  2. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #72

    Eagle51 said:
    Hmm, guess I missed that part ... sorry about that. Thought is was just the IDE ATA/ATAPI Controller / Driver issue.


    No clue, unless it was using the nForce Serial ATA Controllers and getting them under IDE ATA/ATAPI Controller vs Storage Controllers.

    I think you're good to go now, but check the following tutorial about trim if need be - Enable or Disable TRIM Support for Solid State Drives in Windows 10 | Windows 10 Tutorials

    Glad you got it sorted out tho and your welcome :)
    Yeah - if you go back to my post #11 and read from there, you'll see why I chimed into this thread to begin with. I know for a fact that adding the Serial Controller from the link you provided for my chipset download had everything to do with Winsat working this time - after all, what other explanation could there be?

    I did try the Winsat command before and it was before I had tried any of the fixes that you guided me through, and it didn't work back then.

    I wonder if the OP can mark this thread as solved since my problem is gone now -
      My Computer


  3. Posts : 1,471
    Win10 Home x64 - 1809
       #73

    Yeah - if you go back to my post #11 and read from there, you'll see why I chimed into this thread to begin with. I know for a fact that adding the Serial Controller from the link you provided for my chipset download had everything to do with Winsat working this time - after all, what other explanation could there be? I did try the Winsat command before and it was before I had tried any of the fixes that you guided me through.
    Yep, I just didn't go back that far in the thread and I have to agree that using the nForce chipset drivers is what got winsat to run :)
      My Computers


  4. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #74

    Eagle51 said:
    Yep, I just didn't go back that far in the thread and I have to agree that using the nForce chipset drivers is what got winsat to run :)

    You mean, got Winsat to run correctly - I did run it before and Disk Optimization always flagged the Drive as a HDD after running winsat formal.

    I wonder if there is a tutorial for this problem with people who have older systems and decide to install a compatible SSD.

    I mean, this was really hard to figure out and I couldn't of done it until there was an extra set of eyes looking at the problem from a different perspective.
      My Computer


  5. Posts : 1,471
    Win10 Home x64 - 1809
       #75

    You mean, got Winsat to run correctly - I did run it before and Disk Optimization always flagged the Drive as a HDD after running winsat formal.
    Yep .. lol
    I wonder if there is a tutorial for this problem with people who have older systems and decide to install a compatible SSD.
    Don't know, but I doubt there few (if any) formal tutorials, too many legacy chipsets to deal with.
    I mean, this was really hard to figure out and I couldn't of done it until there was an extra set of eyes looking at the problem from a different perspective.
    Yea, I hear ya ... Only reason I had a clue ... I use to have an HP with that exact chipset.
      My Computers


  6. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #76

    Eagle51 said:
    Yea, I hear ya ... Only reason I had a clue ... I use to have an HP with that exact chipset.
    This computer is almost 10 years old, and it is running as fast; if not faster than the day I bought it.
      My Computer


  7. Posts : 18,432
    Windows 11 Pro
       #77

    EyeInTheSky said:
    This computer is almost 10 years old, and it is running as fast; if not faster than the day I bought it.
    @EyeInTheSky,

    Is your SSD identified correctly on the "Defragment and Optimize Drives" screen?

    Should "Defragment and Optimize Drives" be running for an SSD?-capture.jpg
      My Computer


  8. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #78

    NavyLCDR said:
    @EyeInTheSky,

    Is your SSD identified correctly on the "Defragment and Optimize Drives" screen?

    Yes it is. Post #70.


    I'm upset though, I right clicked on NVIDIA nForce Serial ATA Controller and selected to update the driver; which it did:

    Should "Defragment and Optimize Drives" be running for an SSD?-now-what.jpg

    Then it graciously returned me to this:

    Should "Defragment and Optimize Drives" be running for an SSD?-back-where-i-started.jpg


    Notice how mine disappeared from underneath Human Interface Devices.


    What the heck is going on? I'm right back to where I started.


    Disk Optimization still has my SSD listed correctly, but the drive is not being optimized because I can't set AHCI in my BIOS because my chipset doesn't support it.
    Last edited by EyeInTheSky; 25 Aug 2018 at 21:27. Reason: Additional Information.
      My Computer


  9. Posts : 1,471
    Win10 Home x64 - 1809
       #79

    I'm upset though, I right clicked on NVIDIA nForce Serial ATA Controller and selected to update the driver; which it did:
    Not sure why you'd try and update the driver for that legacy nForce chipset, pretty sure you had the latest
    Did the driver vers change or did Win10 just stick them back where it wanted it (under storage controllers) ???
      My Computers


  10. Posts : 1,471
    Win10 Home x64 - 1809
       #80

    BTW .. if you're gonna try and fix again. Instead of going thru what you did last time. I'd try the Add Legacy Hardware first (IDE ATA/ATAPI Controllers and manually add the two nForce Serial ATA Controllers ... driver should still be there). Then I would delete those two under Storage Controllers (don't check the box to remove driver) and hopefully on the reboot it will be back to where it was ... before you tried updating the driver.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:09.
Find Us




Windows 10 Forums