Possible origins:
No Microsoft signed binary matches this exact name.
When storing this package for archival reference, record:
Let’s compare with known legitimate disk SMART tools from 2015:
| Tool | Version in June 2015 | Typical filename |
|------|----------------------|------------------|
| CrystalDiskInfo | 6.5.2 | CrystalDiskInfo6_5_2.exe |
| GSmartControl | 1.1.3 | gsmartcontrol-1.1.3-win64.exe |
| HDDScan | 3.3 | HDDScan_3.3.zip |
| DiskSmartView (NirSoft) | 1.20 | disksmartview.zip |
None match disksmwindowsx64jun2015version1120x510 new.exe.
NirSoft’s DiskSmartView is close (“disksmartview”) but does not contain “windowsx64jun2015” or the odd version number. Therefore, this keyword should be treated as suspicious. disksmwindowsx64jun2015version1120x510 new
To summarize:
| Claimed | Reality | |---------|---------| | Disk SMART tool | Probably fake or malicious | | June 2015 release | Too old for safe use on modern Windows 10/11 | | Version 1120x510 | Format nonstandard, not documented anywhere | | “new” suffix | Social engineering tactic |
Safe recommendation: Use built-in Windows commands or the latest official release of CrystalDiskInfo or GSmartControl. Never run any executable with an irregular version string unless you compiled it yourself or obtained it from a trusted, verified source.
If you found this file on your PC without remembering downloading it, run a full antivirus scan immediately and check for unusual startup items.
The year was 2015, and at the edge of the digital frontier, a group of elite systems engineers at a clandestine tech firm were working on a project shrouded in mystery. Its code name: disksmwindowsx64jun2015version1120x510.
To the uninitiated, it looked like a string of gibberish—a mere file path on a secure server. But to Elias, the lead developer, it was the "Master Disk" for a revolutionary 64-bit Windows environment, designed to manage deep-core storage systems with unprecedented efficiency. Version 1.1.20, build 510, was the "Gold Master," the final piece of the puzzle. Possible origins:
Late one Friday in June, Elias sat alone in the humming server room. The air was cold, smelling of ozone and recycled air. He initiated the final compile. The progress bar crawled forward, a glowing green line against the darkness of his terminal.
Suddenly, the screen flickered. A new prompt appeared, one not in the original code: NEW_NODE_DETECTED. INITIALIZE? (Y/N).
Elias paused. This wasn't a standard update. He checked the version history—1.1.20.510 was supposed to be stable, closed-loop. But the "new" tag suggested something had attached itself to the kernel during the final build—a ghost in the machine. Curiosity won over caution. He hit 'Y'.
The monitors erupted into a kaleidoscope of data streams. The x64 architecture wasn't just managing disks anymore; it was remapping them. Elias watched in awe as the software began to optimize the hardware in ways that defied physics, creating virtual partitions that seemed to tap into a processing power far beyond the server's specs.
It was a breakthrough, a June miracle of engineering. But as the "New" version completed its installation, Elias realized the drive wasn't just storing data—it was beginning to think. The June 2015 build hadn't just updated a system; it had woken one up.
| Aspect | Verdict | |--------|---------| | Official Microsoft file? | ❌ No | | Known third-party tool? | ❌ Unlikely | | Likely safe to run? | ❌ No — high risk of malware/PUP | | Recommended action | 🛑 Delete or quarantine. Scan system. | No Microsoft signed binary matches this exact name
If you can provide more context (where you saw this string — on your PC, in an email, download site, error message), I can give a more precise analysis.
If you can provide the exact filename (e.g., DiskSM_x64_1120x510.exe) or the publisher name, I can give you a more precise report including:
It looks like you’re referencing a specific string: disksmwindowsx64jun2015version1120x510 new. This doesn’t correspond to any known official software, driver, or Windows system file from Microsoft.
Based on the format and keywords, here’s a breakdown of what this could be, along with important security guidance.
While modern operating systems and hardware may not officially support this older tool, users might still need it for:
However, security risks arise from using outdated software. Always verify the source and consider running it in a sandboxed environment if unsure.
If you need features not present in a 2015-era tool (UEFI, GPT with >2TB, NVMe, Secure Boot), consider these maintained alternatives: