Windows Cannot Open images or Microsoft Word documents

I’m running into a real headache here—I can't get my photos or Microsoft Word documents to open properly. It isn't everything, though; it's specifically targeting files that have been sitting on my D: drive for a long time. This whole mess started right after I finished installing new Windows updates. Everything I've created recently works perfectly fine, but the older stuff is a disaster. When I try to launch an old Word doc, Microsoft Word actually opens, but then it just throws this annoying pop-up window at me about some kind of encoding error. I'm feeling a bit stuck. Any advice or help would be sincerely appreciated! 👍

Is that a second partition (D🙂) or an entirely separate drive?
If it’s a different drive, I'd suggest installing CrystalDiskInfo to check its health status.

Just a hunch—it feels like the data on that partition might be fragmented or corrupted, though there could be other issues at play.
When you try to open those images, what kind of error does it give you? Is it just "Windows Cannot Open" or something more specific?
Also, which version of Microsoft Word were those old .doc files originally created in, and which version are you using to try and open them now?

So, here's the deal... Windows Cannot Open
one specific drive, though it's just on a different partition. As far as Microsoft Word goes, I suspect those files were created back in 2013, but I'm currently running 2010. That actually makes sense to me, but it makes zero sense why it won't even let me view my photos. Does anyone have a fix for this?

analogwolf12 said:Regarding Microsoft Word, I think these were made with the 2013 version, but I'm running 2010.

😵 If you're questioning your own sanity, don't worry—your logic holds up. Of course 2010 isn't going to be able to open a newer file format...

As for the images, what format are we talking about and what are you using to view them? Right-click the image icon and hit properties; check what it says there. You should see an extension like something.jpg and it’ll show which program is set to handle it. You probably just need to install the right software or adjust your preferences to tell Windows which program to use by default. Alternatively, just right-click the image, select open with..., pick the program you want, and make sure to check that box to apply it to all files of that type...

Regarding Microsoft Word documents, you're basically looking at two main formats: .doc and .docx.

The older .doc files generally need to be opened using versions ranging from '97 up through 2013.
As for .docx, those should open by default in anything from 2007 to 2013—though I guess you could install a plugin if you're stuck using 2000 or 2003.

Even an JPG file should be easy enough for a modern version of Windows to handle.

I'm still a bit skeptical about whether the data on that partition actually got scattered, but I suppose you should just keep trying things.

darkowl72 said:😵 If you’re second-guessing your own reasoning, don't sweat it—your logic is perfectly sound. It makes complete sense that a system from 2010 wouldn't be able to handle a much newer file format...

As for those images, what specific format are we talking about, and which app are you using to view them? Try this: right-click the image icon and hit Properties. I need to know exactly what it says there—it should list an extension like something.jpg and show which program is assigned to it. You might just need to reinstall the software you usually use, or perhaps tweak your preferences to tell Windows which program should be your default for images. Another quick fix: right-click the image, select Open with..., pick the program you prefer, and make sure to check that little box that says "Always use this app to open .jpg files." That should set things right for all similar files...

Yeah... it says jpg, and I'm using Windows Photo Viewer (that's my go-to), and it works just fine since it handles all my newer photos without any issues.

George Sanders37 said:When you're dealing with Microsoft Word documents, you're basically looking at two main formats: .doc and .docx.

To get those old .doc files working, you'll generally need a version of Microsoft Word ranging from '97 up through 2013.
As for .docx, those should open without a hitch in anything from 2007, 2010, or 2013, though you can always grab a plugin if you're stuck using the ancient 2000 or 2002/2003 versions.

Even a standard JPG should be easy enough for a modern Windows installation to handle.

Personally, I’m still a bit skeptical about whether the data on that partition actually got scattered or corrupted, but you should definitely keep digging.

Is there any hope of recovery here, or is it all gone?

It’s pretty hard to give much advice this far out—I just don't know what went wrong or what's actually causing the issue.

Maybe you could try eliminating variables one by one. Copy those documents and photos you definitely can't get into onto a flash drive and see if they'll open on a different computer. If you run into the same symptoms there, then you'll know the problem lies with the files themselves. You might also want to run an error-check on the drive—and I guess it wouldn't hurt to check the drive's health with CrystalDiskInfo, just to be safe.

Check the status. Right-click the icon, go to Properties, then Tools, and hit Check disk; basically, Properties > Tools > Check now. See if it flags any errors, but if it asks you to fix them—don't let it. Just write down whatever it reports and tell me...

George Sanders37 said:It’s tough to offer much help without knowing what actually went wrong or what triggered the issue in the first place.

You can try to narrow things down through a bit of trial and error. Grab a USB flash drive and copy over those documents and photos you definitely can't access, then try opening them on a completely different computer. If the exact same thing happens there, then you've confirmed the problem lies with the files themselves. You should also run an error check on the drive and, just to be safe, scan everything with CrystalDiskInfo.

Alright, I'll give that a shot. I'm honestly not sure how to perform an error check, though. And how am I supposed to use this CrystalDiskInfo tool? I downloaded it, but now I'm just staring at it wondering what comes next...

darkowl72 said:Check the status. Right-click the icon, go to Properties, then hit the Tools tab, and select Check now. See if it reports any errors. If it asks you if you want to fix them—don't say yes yet. Just write down whatever error message pops up and let us know what it says...

Man, which icon? When I right-click on an actual photo file, I don't see those options (Tools, Check now...). All I get is General, Security, and Details.😵

Not the image, I mean drive D...

says no errors were found. Still, I went ahead and ran the check just to be absolutely certain. I'll let you know what comes back.

- EventData

Checking file system on stage 1: Examining basic file system structure ... Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x2d3c66 for possibly 0x329 clusters. Found corrupt basic file structure for "\JB CM10\SlideIt-v5.1.crk.ChelpuS.v.2.0.rar <0x6,0x1ba6>" ... repaired online. File "\$Secure <0x9,0x9>" and file "\JB CM10\SlideIt-v5.1.crk.ChelpuS.v.2.0.rar <0x6,0x1ba6>" both own logical clusters [0x2d3d3f, 0x2d3d90) ... queued for offline repair. 25600 file records processed. File verification completed. 24 large file records processed. 0 bad file records processed. stage 2: Examining file name linkage ... Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins <0x1,0xd83>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins <0x1,0xd83>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins <0x1,0xd83>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins <0x1,0xd83>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\Android_Battery <0x1,0xd84>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\Android_Battery <0x1,0xd84>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\anotherbattery <0x1,0xd92>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\anotherbattery <0x1,0xd92>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\anotherbattery <0x1,0xd92>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\anotherbattery <0x1,0xd92>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\blackbatt2 <0x1,0xda0>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\blackbatt2 <0x1,0xda0>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\blackbattery <0x1,0xdae>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\blackbattery <0x1,0xdae>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.PNG") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.URL") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.PNG") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.URL") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw battery skins\HoneyBat <0x1,0xdbc>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\3DWeather(stigmata) <0x1,0xdcd>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\3DWeather(stigmata) <0x1,0xdcd>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\3DWeather(stigmata) <0x1,0xdcd>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.TXT") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\3DWeather(stigmata) <0x1,0xdcd>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\ANDRODeNa_GLASS_WEATHER <0x1,0xde6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\ANDRODeNa_GLASS_WEATHER <0x1,0xde6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\ANDRODena_Weather_Pack <0x1,0xdfe>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\ANDRODena_Weather_Pack <0x1,0xdfe>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\boca <0x1,0xe16>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\boca <0x1,0xe16>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\DarkLudi <0x1,0xe2e>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\DarkLudi <0x1,0xe2e>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\Dharma <0x1,0xe46>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\Dharma <0x1,0xe46>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\DirtyPaper <0x1,0xe5e>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\Samsung backup\beaut widg skins\bw weather skins\wskins\DirtyPaper <0x1,0xe5e>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\life stories <0x7,0x19b3>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.TXT") in index "$I30" of directory "\life stories <0x7,0x19b3>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\life stories <0x7,0x19b3>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.TXT") in index "$I30" of directory "\life stories <0x7,0x19b3>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.HTML") in index "$I30" of directory "\life stories\life stories <0x3,0x19b6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.HTM") in index "$I30" of directory "\life stories\life stories <0x3,0x19b6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.PNG") in index "$I30" of directory "\life stories\life stories <0x3,0x19b6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.URL") in index "$I30" of directory "\life stories\life stories <0x3,0x19b6>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_DECRYPT.TXT") in index "$I30" of directory "\JB CM10 <0xb,0x1a93>" ... repaired online. Found an unneeded link ($FILE_NAME: "HELP_D~1.TXT") in index "$I30" of directory "\JB CM10 <0xb,0x1a93>" ... repaired online. 28546 index entries processed. Index verification completed. Found 3 lost files (\Samsung backup\beaut widg skins\bw battery skins\anotherbattery\anotherbattery.txt <0x1,0xd94>, ...); requesting reconnection to index "$I30" of directory "\??\D:\found.000" ... queued for offline repair. stage 3: Examining security descriptors ... Found corrupt security descriptor entry at offset 0 in \$Secure <0,0x9>:$SDS ... queued for offline repair. 25600 file SDs/SIDs processed. Found 5 files (\$MFT <0x1,0>, \$MFTMirr <0x1,0x1>, \$LogFile <0x2,0x2>, \$Bitmap <0x6,0x6>, ...) which refer to a non-existent security descriptor 0x100 ... queued for offline repair. Found 7 files (\$Volume <0x3,0x3>, \$Extend <0xb,0xb>, \$Extend\$Quota <0x1,0x18>, \$Extend\$ObjId <0x1,0x19>, ...) which refer to a non-existent security descriptor 0x101 ... queued for offline repair. Found 4 files (\$Extend\$RmMetadata <0x1,0x1b>, \$Extend\$RmMetadata\$TxfLog <0x1,0x1d>, \$Extend\$RmMetadata\$Txf <0x1,0x1e>, \$Extend\$RmMetadata\$TxfLog\$Tops <0x1,0x1f>) which refer to a non-existent security descriptor 0x102 ... queued for offline repair. File \$Extend\$RmMetadata\$TxfLog\$TxfLog.blf <0x1,0x20> refers to a non-existent security descriptor 0x103 ... queued for offline repair. Found 2 files (\$Extend\$RmMetadata\$TxfLog\$TxfLogContainer0000 0000000000000001 <0x1,0x21>, ...) which refer to a non-existent security descriptor 0x104 ...

\DOCUMENT\20100520 <0x1,0x2ca>, \DOCUMENT\gegl-0.0 <0x1,0x2d0>, ...) which point to a missing security descriptor 0x110 ... set for offline repair. I found 2935 files (\Convert\Dconvert.ico <0x1,0x2a8>, \Convert\desktop.ini <0x1,0x2a9>, \DOCUMENT\fl2_sc-pop84_resized.gif <0x1,0x2b8>, \DOCUMENT\ScreenShot002.bmp <0x1,0x2c1>, ...) which point to a missing security descriptor 0x111 ... set for offline repair. File \$RECYCLE.BIN\S-1-5-21-3292123578-443679365-3287061529-1000 <0x2,0x17c8> points to a missing security descriptor 0x112 ... set for offline repair. File \$RECYCLE.BIN\S-1-5-21-3292123578-443679365-3287061529-1000\desktop.ini <0x1,0x17c9> points to a missing security descriptor 0x113 ... set for offline repair. I found 1339 files (\torrent\New folder (3)\TuneUp.Utilities.2011.v10.0.4200.98.Incl.Keygen-FFF ELEAQUIN.1.torrent <0x4,0x64>, ...) which point to a missing security descriptor 0x116 ... set for offline repair. I found 2 files (\torrent <0x3,0x17cb>, \torrent\New folder (3) <0x1,0x1f22>) which point to a missing security descriptor 0x118 ... set for offline repair. I found 2 files (\IO.SYS <0xb,0x18d5>, \MSDOS.SYS <0x9,0x18da>) which point to a missing security descriptor 0x11a ... set for offline repair. I found 2 files (\$AVG <0x1a,0x19a7>, \$AVG\$VAULT <0x8,0x19a8>) which point to a missing security descriptor 0x123 ... set for offline repair. File \$RECYCLE.BIN\S-1-5-21-1800988149-1532199728-3222301046-1000 <0xb,0x35fb> points to a missing security descriptor 0x12e ... set for offline repair. File \$RECYCLE.BIN\S-1-5-21-1800988149-1532199728-3222301046-1000\desktop.ini <0x4,0x35fc> points to a missing security descriptor 0x12f ... set for offline repair. I found 221 files (\torrent\pics New York <0x3,0x2e>, \Documents\Tomi\3rd grade, test <0x3,0x63>, \Documents\Tomi\2nd grade, test <0x2,0x6a>, \Richard Pryor Live on the Sunset Strip <0x8,0x8b>, ...) which point to a missing security descriptor 0x130 ... set for offline repair. I found 2 files (\$RECYCLE.BIN\S-1-5-21-1800988149-1532199728-3222301046-1000\$IN6OMX3.iso <0xb,0x1817>, ...) which point to a missing security descriptor 0x133 ... set for offline repair. I found 3313 files (\JB CM10\filepush.v1.2.1-androget.com.apk <0x3,0x2b>, ...) which point to a missing security descriptor 0x136 ... set for offline repair. I found 2 files (\System Volume Information\MountPointManagerRemoteDatabase <0x3,0x17da>, ...) which point to a missing security descriptor 0x13d ... set for offline repair. I found 8 files (\System Volume Information\_restore{F67CC82A-855B-4C77-BB59-BC289E89EBFB}\RP1\RestorePointSize <0xa,0x17db>, ...) which point to a missing security descriptor 0x169 ... set for offline repair. I found 3 files (\boot.ini <0x6,0x17dd>, \ntldr <0x1e,0x31c8>, \NTDETECT.COM <0x1d,0x31c9>) which point to a missing security descriptor 0x16b ... set for offline repair. I found 5 files (\Boot\BOOTSTAT.DAT <0xa,0x18e9>, \Boot\BCD <0x2,0x600d>, \Boot\BCD.LOG <0x3,0x600e>, \Boot\BCD.LOG1 <0x2,0x600f>, ...) which point to a missing security descriptor 0x16f ... set for offline repair. I found 80 files (\Boot\bg-BG\bootmgr.exe.mui <0x5c,0x184>, \Boot\cs-CZ\bootmgr.exe.mui <0x5b,0x192>, \Boot\cs-CZ\memtest.exe.mui <0x5b,0x193>,
00640000EA49000051870000000000006E0500000000000000 00000000000000

--------------------------------------------------------------------------------

Binary data:

In Words

0000: 00006400 000049EA 00008751 00000000
0010: 0000056E 00000000 00000000 00000000

In Bytes

0000: 00 64 00 00 EA 49 00 00 .d..êI..
0008: 51 87 00 00 00 00 00 00 Q‡......
0010: 6E 05 00 00 00 00 00 00 n.......
0018: 00 00 00 00 00 00 00 00 ........

Man... looks like George Sanders37 was right all along. That partition just completely disintegrated... 😱

So, what’s the damage once the scan wraps up? Have you had a chance to see if anything is salvageable, or is everything still totally trashed?

darkowl72 said:Man... looks like George Sanders37 was right on the money. That partition just completely disintegrated... 😱

So, what's the status once the scan finishes? Have you had a chance to see if any files are actually accessible, or is everything still totally wiped out?

I haven't checked yet. You told me to just report whatever the error messages say without digging too deep. I'll get on that right now.

Running a check on the file system on stage 1... I've gone through 25,600 file records. Everything looks solid there. Processed 24 large file records, and thankfully, zero bad records were found. Moving on to stage 2 to look at file name linkage... finished processing 28,548 index entries. Verification complete. Now, stage 3: checking those security descriptors... All good. Verified 1,475 data files. CHKDSK is now running a check on the Usn Journal... That's 40,225,104 USN bytes processed. Usn Journal verification completed. The good news? Windows Has scanned the file system and everything is perfectly clean. No extra steps needed here. Total disk capacity is sitting at 327,677,951 KB. There's 155,334,820 KB spread across 17,436 files. Indexes are taking up 9,408 KB within 1,476 entries. The system itself is using about 141,295 KB, and the log file is holding onto 65,536 KB. This leaves us with 172,192,428 KB of free space. Each allocation unit is 4,096 bytes, with 81,919,487 total units on the drive and 43,048,107 currently available. ---------------------------------------------------------------------- stage 1: Examining basic file system structure ... stage 2: Examining file name linkage ... stage 3: Examining security descriptors ... Windows Has scanned the file system and found no problems. No further action is required.
00640000EC49000050870000000000006E0500000000000000 00000000000000

--------------------------------------------------------------------------------

Binary data:

In Words

0000: 00006400 000049EC 00008750 00000000
0010: 0000056E 00000000 00000000 00000000

In Bytes

0000: 00 64 00 00 EC 49 00 00 .d..ìI..
0008: 50 87 00 00 00 00 00 00 P‡......
0010: 6E 05 00 00 00 00 00 00 n.......
0018: 00 00 00 00 00 00 00 00 ........

It says it's fixed, but honestly, I still can't get anything to work.

I’d love to get an opinion from someone a bit more experienced than I am on this—maybe you've run into this before? Have you ever tried creating extra partitions only to have the process crash or just fail to finish properly? A corrupted file table isn't exactly common, so it might be a sign that something is actually wrong with the drive itself.

Have you checked the drive stats using CrystalDiskInfo? You should be able to grab a screenshot that looks something like this: http://crystalmark.info/software/Cry...mages/Main.png

On that screen, the drive health status should show up as Healthy/Good, and the little circles in the list below should all be the same color—either blue or green. If one of those circles stands out or looks different, that’s usually a red flag that the drive is struggling.

I didn't bother setting up any extra partitions, yet when I ran CrystalDiskInfo, the results were almost identical to the screenshot you posted. Everything is showing up blue.