Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hard drive says its full when it isn't?


  • This topic is locked This topic is locked
10 replies to this topic

#1 boltactionmike

boltactionmike

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 19 February 2015 - 09:03 PM

Hello, I have been having a strange problem where my computer seems to think its hard drive is full. I have used WinDirstat and spacesniffer to try and find abnormally large files I dont recognize but to no avail. I have ran CC cleaner, AWDcleaner, malwarebytes, ADaware, and avast antivirus (boot time and full scan) trying to track something down. I have also ran an "error check" and "defragment' on the drive and nothing was found.

Both WinDirstat and spacesniffer determined there to be 209GB of data on the drive, where under my computer and under properties, the hard drive belives it has 431GB of data. that leaves me only 21GB left on the drive. Help is very much appreciated, thank you guys.

 

this was the error log for spacesniffer:

 

WARN  16:24:16 - Unable to examine C:\Config.Msi (Access is denied. - code 5)
WARN  16:24:28 - Unable to examine C:\MSOCache (Access is denied. - code 5)
WARN  16:24:30 - Unable to examine C:\PerfLogs (Access is denied. - code 5)
WARN  16:24:39 - Unable to examine C:\Program Files (x86)\Google\CrashReports (Access is denied. - code 5)
WARN  16:25:06 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\2427C246DCF85A06DD675914EDA68038_BAFDBEF941F3E70975B098D4DBE3F67B (The directory name is invalid. - code 267)
WARN  16:25:06 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content\2427C246DCF85A06DD675914EDA68038_BAFDBEF941F3E70975B098D4DBE3F67B (The directory name is invalid. - code 267)
WARN  16:25:10 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\5B565E5A03C1711296156E2E5BE2718C_24888EA7BA12370D6953777D73052E81 (The directory name is invalid. - code 267)
WARN  16:25:11 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content\5B565E5A03C1711296156E2E5BE2718C_24888EA7BA12370D6953777D73052E81 (The directory name is invalid. - code 267)
WARN  16:25:11 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData\C9E3282A673263848AB7F0C007FD3AF1_C3EA707C77B31FA641C05A1712998054 (The directory name is invalid. - code 267)
WARN  16:25:12 - Unable to examine C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content\C9E3282A673263848AB7F0C007FD3AF1_C3EA707C77B31FA641C05A1712998054 (The directory name is invalid. - code 267)
WARN  16:25:53 - Unable to examine C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 (Access is denied. - code 5)
WARN  16:25:53 - Unable to examine C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore (Access is denied. - code 5)
WARN  16:25:53 - Unable to examine C:\ProgramData\Microsoft\Network\Downloader (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Search\Data (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\Power Efficiency Diagnostics (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_0x80070652_c455dc1274259edcfd62ea79431c2fe2cd5ba54_17a176e6 (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_94abc61042a953e382c748b64f2bfff5d97aec51_cab_195299ff (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_08f679e7 (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_09728db9 (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_0abc4058 (Access is denied. - code 5)
WARN  16:25:54 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_0d220f65 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_0d503432 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_0d79c65c (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_15301193 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_1ea4cf8c (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_20fb2c51 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_244717a0 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_2dcc1dd2 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_3dfeee70 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_426cf1d0 (Access is denied. - code 5)
WARN  16:25:55 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_985d3fe7340b894a9c366dff441c85b17a260d1_44c9992d (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_1_d1e3ca32456fc9a2a6234ec3f825935fedbc9a1_cab_1c4164cd (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.320_2f6834f5ad080777588737322b1dbccbd6bccdd_046197c6 (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.320_bc75189718b03ab1c16ae15dcb6bcb4d583de_11aebd41 (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80240016_529beb742b17fa98635f83435f9791538c4fa_02e8d6be (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80240016_529beb742b17fa98635f83435f9791538c4fa_02e8edc0 (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_8024001f_90a685ca535d05e2e4bc1b63f35dca7e176e2_0461a812 (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows Defender (Access is denied. - code 5)
WARN  16:25:56 - Unable to examine C:\ProgramData\Microsoft\Windows NT\MSFax (Access is denied. - code 5)
WARN  16:25:57 - Unable to examine C:\Recovery (Access is denied. - code 5)
WARN  16:26:20 - Unable to examine C:\System Volume Information (Access is denied. - code 5)
WARN  16:26:31 - Unable to examine C:\Windows\AppCompat\Appraiser\Telemetry (Access is denied. - code 5)
WARN  16:26:31 - Unable to examine C:\Windows\AppCompat\Programs (Access is denied. - code 5)
WARN  16:26:43 - Unable to examine C:\Windows\CSC\v2.0.6 (Access is denied. - code 5)
WARN  16:26:48 - Unable to examine C:\Windows\LiveKernelReports (Access is denied. - code 5)
WARN  16:26:48 - Unable to examine C:\Windows\Logs\HomeGroup (Access is denied. - code 5)
WARN  16:26:48 - Unable to examine C:\Windows\Logs\SystemRestore (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\Minidump (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\ModemLogs (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\PLA\Reports (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\PLA\Rules (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\PLA\Templates (Access is denied. - code 5)
WARN  16:26:53 - Unable to examine C:\Windows\Prefetch (Access is denied. - code 5)
WARN  16:26:54 - Unable to examine C:\Windows\security\audit (Access is denied. - code 5)
WARN  16:26:54 - Unable to examine C:\Windows\ServiceProfiles\LocalService (Access is denied. - code 5)
WARN  16:26:54 - Unable to examine C:\Windows\ServiceProfiles\NetworkService (Access is denied. - code 5)
WARN  16:27:13 - Unable to examine C:\Windows\System32\appmgmt\MACHINE (Access is denied. - code 5)
WARN  16:27:13 - Unable to examine C:\Windows\System32\appmgmt\S-1-5-18 (Access is denied. - code 5)
WARN  16:27:13 - Unable to examine C:\Windows\System32\com\dmp (Access is denied. - code 5)
WARN  16:27:13 - Unable to examine C:\Windows\System32\config (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\ias (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\LogFiles\Fax\Incoming (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\LogFiles\Fax\Outgoing (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\LogFiles\Firewall (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\LogFiles\HTTPERR (Access is denied. - code 5)
WARN  16:27:25 - Unable to examine C:\Windows\System32\LogFiles\WMI (Access is denied. - code 5)
WARN  16:27:26 - Unable to examine C:\Windows\System32\Msdtc (Access is denied. - code 5)
WARN  16:27:26 - Unable to examine C:\Windows\System32\NetworkList (Access is denied. - code 5)
WARN  16:27:27 - Unable to examine C:\Windows\System32\spool\PRINTERS (Access is denied. - code 5)
WARN  16:27:27 - Unable to examine C:\Windows\System32\Tasks (Access is denied. - code 5)
WARN  16:27:27 - Unable to examine C:\Windows\System32\wbem\MOF (Access is denied. - code 5)
WARN  16:27:27 - Unable to examine C:\Windows\System32\wdi (Access is denied. - code 5)
WARN  16:27:27 - Unable to examine C:\Windows\System32\wfp (Access is denied. - code 5)
WARN  16:27:28 - Unable to examine C:\Windows\SysWOW64\com\dmp (Access is denied. - code 5)
WARN  16:27:28 - Unable to examine C:\Windows\SysWOW64\config (Access is denied. - code 5)
WARN  16:27:29 - Unable to examine C:\Windows\SysWOW64\Msdtc (Access is denied. - code 5)
WARN  16:27:29 - Unable to examine C:\Windows\SysWOW64\NetworkList (Access is denied. - code 5)
WARN  16:27:29 - Unable to examine C:\Windows\SysWOW64\Tasks (Access is denied. - code 5)
WARN  16:27:30 - Unable to examine C:\Windows\Temp (Access is denied. - code 5)
WARN  16:29:09 - Unable to examine C:\Windows\Temp\gui5191.tmp (The directory name is invalid. - code 267)
WARN  16:34:07 - Unable to examine C:\Windows\Temp\GURDFE3.tmp (The directory name is invalid. - code 267)
WARN  16:36:59 - Unable to examine C:\MSI97740.tmp (The system cannot find the path specified. - code 3)
WARN  16:36:59 - Unable to examine C:\Windows\Temp\~DFDB9D28FF40110EC5.TMP (The directory name is invalid. - code 267)
WARN  16:37:01 - Unable to examine C:\Windows\Temp\~DF27CDFD5973DA617E.TMP (The directory name is invalid. - code 267)
WARN  16:37:01 - Unable to examine C:\Config.Msi\197743.rbs (The directory name is invalid. - code 267)
WARN  16:37:11 - Unable to examine C:\Config.Msi\MSIAEB8.tmp (The system cannot find the path specified. - code 3)
WARN  16:39:15 - Unable to examine C:\Windows\Temp\GUM91EB.tmp (Access is denied. - code 5)
WARN  16:39:15 - Unable to examine C:\Windows\Temp\GUM91EB.tmp (Access is denied. - code 5)
WARN  16:39:15 - Unable to examine C:\Windows\Temp\GUT91EC.tmp (The directory name is invalid. - code 267)
WARN  16:39:15 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdate.exe (The directory name is invalid. - code 267)
WARN  16:39:16 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleCrashHandler.exe (The directory name is invalid. - code 267)
WARN  16:39:16 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdate.dll (The directory name is invalid. - code 267)
WARN  16:39:17 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\npGoogleUpdate3.dll (The directory name is invalid. - code 267)
WARN  16:39:17 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateHelper.msi (The directory name is invalid. - code 267)
WARN  16:39:17 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateBroker.exe (The directory name is invalid. - code 267)
WARN  16:39:17 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateOnDemand.exe (The directory name is invalid. - code 267)
WARN  16:39:17 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateComRegisterShell64.exe (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateWebPlugin.exe (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\psmachine.dll (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\psmachine_64.dll (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\psuser.dll (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\psuser_64.dll (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleCrashHandler64.exe (The directory name is invalid. - code 267)
WARN  16:39:18 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_am.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ar.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_bg.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_bn.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ca.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_cs.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_da.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_de.dll (The directory name is invalid. - code 267)
WARN  16:39:19 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_el.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_en.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_en-GB.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_es.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_es-419.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_et.dll (The directory name is invalid. - code 267)
WARN  16:39:20 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_fa.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_fi.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_fil.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_fr.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_gu.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_hi.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_hr.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_hu.dll (The directory name is invalid. - code 267)
WARN  16:39:21 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_id.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_is.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_it.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_iw.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ja.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_kn.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ko.dll (The directory name is invalid. - code 267)
WARN  16:39:22 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_lt.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_lv.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ml.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_mr.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ms.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_nl.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_no.dll (The directory name is invalid. - code 267)
WARN  16:39:23 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_pl.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_pt-BR.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_pt-PT.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ro.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ru.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_sk.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_sl.dll (The directory name is invalid. - code 267)
WARN  16:39:24 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_sr.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_sv.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_sw.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ta.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_te.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_th.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_tr.dll (The directory name is invalid. - code 267)
WARN  16:39:25 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_uk.dll (The directory name is invalid. - code 267)
WARN  16:39:26 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_ur.dll (The directory name is invalid. - code 267)
WARN  16:39:26 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_vi.dll (The directory name is invalid. - code 267)
WARN  16:39:26 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_zh-CN.dll (The directory name is invalid. - code 267)
WARN  16:39:26 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\goopdateres_zh-TW.dll (The directory name is invalid. - code 267)
WARN  16:39:26 - Unable to examine C:\Windows\Temp\GUM91EB.tmp\GoogleUpdateSetup.exe (The directory name is invalid. - code 267)
WARN  16:39:31 - Unable to examine C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles\00010009.wid (The directory name is invalid. - code 267)
WARN  16:39:31 - Unable to examine C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles\00010009.ci (The directory name is invalid. - code 267)
WARN  16:40:07 - Unable to examine C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles\0001000A.wid (The directory name is invalid. - code 267)
WARN  16:40:07 - Unable to examine C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles\0001000A.ci (The directory name is invalid. - code 267)
WARN  16:40:10 - Unable to examine C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles\0001000A.dir (The directory name is invalid. - code 267)
 

So, should I just go through this list file by file and see if anything is taking up a lot of space?

once again thank you in advance and your time is very much appreciated.

~mike


Edited by boltactionmike, 19 February 2015 - 09:05 PM.


BC AdBot (Login to Remove)

 


m

#2 JohnC_21

JohnC_21

  • Members
  • 21,638 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:54 AM

Posted 19 February 2015 - 10:17 PM

I believe you have a serious infection. I would start a thread in the Malware Removal Forum. Read the sticky posts and attach the appropriate logs.

 

Edit: Look under Virus Characteristics here. You will see the temp files created are similar to yours and your files are being denied access.

 

http://home.mcafee.com/virusinfo/virusprofile.aspx?key=1037146#none


Edited by JohnC_21, 19 February 2015 - 10:19 PM.


#3 Taikoh

Taikoh

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:In front of a laptop
  • Local time:12:54 AM

Posted 19 February 2015 - 10:41 PM

Out of curiosity, does running SpaceSniffer as an administrator get rid of those error messages? I've encountered that many times and each time I'd forgotten to run it as an admin.  :blush:



#4 boltactionmike

boltactionmike
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 19 February 2015 - 10:51 PM

Thank you john, I will try and move it over there and see if anyone can help me out. and I will take a look at the link you gave me. thank you very much.

and @ Taiko, I dont see an option to run as admin and I only have one account on my windows so hopefully it is automatically ran as admin?



#5 Taikoh

Taikoh

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:In front of a laptop
  • Local time:12:54 AM

Posted 19 February 2015 - 10:55 PM

You've got to right-click it and select "Run as Administrator" in order to run it with administrative privileges. Either that, or right-click the application and go to Properties, then at the bottom of the "Compatibility" tab, check the "Run this program as an administrator" checkbox and press Ok. That'll make sure that SpaceSniffer always runs with administrative privileges if you don't want to right-click it each time.  :P



#6 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,701 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:12:54 AM

Posted 19 February 2015 - 10:57 PM

Hello boltactionmike,

 

To elaborate on what John said, the sticky in question is here: http://www.bleepingcomputer.com/forums/t/34773/preparation-guide-for-use-before-using-malware-removal-tools-and-requesting-help/

 

and the forum to create the new topic in is here: http://www.bleepingcomputer.com/forums/f/22/virus-trojan-spyware-and-malware-removal-logs/

 

Orange Blossom :cherry:


Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript

#7 boltactionmike

boltactionmike
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 19 February 2015 - 11:06 PM

You guys are very fast and very helpful, I really appreciate it. I opened a new thread under malware/virus and used the steps from the sticky provided. Hopefully someone will have some input!

thank you all for the help!



#8 boltactionmike

boltactionmike
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 19 February 2015 - 11:22 PM

So I ended up running spacesniffer again as admin and all the errors disappeared....

looking like the stuff in blue is the suspect but I have no clue.

this is what it looked like

http://s1381.photobucket.com/user/boltactionmike/media/suspect_zpslsww19jf.png.html?sort=3&o=0



#9 boltactionmike

boltactionmike
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:54 PM

Posted 19 February 2015 - 11:58 PM

So it turns out it was a virus that had to do with system restore points. deleted all my system restore points, restarted the computer and all is well. easy fix! thank you all for your time and energy. I am not sure how to mark this solved.

:love4u:



#10 Taikoh

Taikoh

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:In front of a laptop
  • Local time:12:54 AM

Posted 20 February 2015 - 12:04 AM

Oh awesome, glad to see you were able to get it fixed!  :lol:



#11 hamluis

hamluis

    Moderator


  • Moderator
  • 54,839 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:54 PM

Posted 20 February 2015 - 09:44 AM

MRL topic, http://www.bleepingcomputer.com/forums/t/567675/hard-drive-says-its-full-when-it-isnt/#entry3633614 .

 

This topic is closed to avoid confusion.

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users