{"id":441,"date":"2009-11-25T10:53:37","date_gmt":"2009-11-25T17:53:37","guid":{"rendered":"http:\/\/kmwoley.com\/blog\/?p=441"},"modified":"2009-11-25T11:02:18","modified_gmt":"2009-11-25T18:02:18","slug":"where-to-find-chkdsk-results-in-vista-windows-7","status":"publish","type":"post","link":"https:\/\/kmwoley.com\/blog\/where-to-find-chkdsk-results-in-vista-windows-7\/","title":{"rendered":"Where to find CHKDSK results in Vista, Windows 7"},"content":{"rendered":"<p><a href=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/powershellchkdsk8.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px\" title=\"powershell-chkdsk\" border=\"0\" alt=\"powershell-chkdsk\" src=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/powershellchkdsk-thumb8.jpg\" width=\"244\" height=\"168\" \/><\/a><\/p>\n<p>My recent hard disk failure made me realize that I had no idea where to find the CHDSK logs that are created when Windows runs CHKDSK at boot. In my case, I had just installed a drive that had a bunch of NTFS corruptions caused by a different computer.<\/p>\n<p>Below I walk though what I think is the easiest way to find the CHKDSK logs (and more) which are available in the Windows Event Log.<\/p>\n<p> <!--more-->  <\/p>\n<p><strong><u>Short Answer<\/u> <\/strong><\/p>\n<blockquote>\n<p><strong>1. Start Windows PowerShell as Administrator<\/strong>       <br \/><a href=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/image.png\"><strong><img loading=\"lazy\" decoding=\"async\" style=\"border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px\" title=\"image\" border=\"0\" alt=\"image\" src=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/image-thumb.png\" width=\"187\" height=\"244\" \/><\/strong><\/a> <\/p>\n<\/blockquote>\n<blockquote>\n<p><strong>2. Type in the following at the prompt:<\/strong>       <br \/><font color=\"#0000a0\" face=\"Courier New\">get-winevent -FilterHashTable @{logname=&quot;Application&quot;; id=&quot;1001&quot;}| ?{$_.providername \u2013match &quot;wininit&quot;} | fl timecreated, message<\/font><\/p>\n<p><em>Note: if you want to limit the search to just the recent events, you can add the <font face=\"Courier New\">starttime=&quot;11\/25\/2009&quot;<\/font> to the FilterHashTable parameter above.<\/em><\/p>\n<p><em><\/em><a href=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/powershellchkdsk9.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px\" title=\"powershell-chkdsk\" border=\"0\" alt=\"powershell-chkdsk\" src=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/powershellchkdsk-thumb9.jpg\" width=\"413\" height=\"284\" \/><\/a>       <\/p>\n<\/blockquote>\n<p><strong><\/strong><\/p>\n<p><strong><u>Long Answer<\/u><\/strong><\/p>\n<p><strong>Windows Event Log      <br \/><\/strong>Windows stores the results of CHKDSK, among other things, in the Windows Event Log. This is a good thing because the Event Log does a great job managing a lot of data. Given that so many different parts of the OS are involved in writing to the disk, it wouldn\u2019t make sense to write the results in several different text files. You\u2019d never be able to find out anything. The only downside to this is that you have to learn to use the Event Log, which isn\u2019t that hard.<\/p>\n<p><strong>Windows PowerShell &amp; the Event Log      <br \/><\/strong>The easiest way to read the Event Log is to use <a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/aa973757(VS.85).aspx\" target=\"_blank\">Windows PowerShell<\/a> and the <a href=\"http:\/\/blogs.msdn.com\/powershell\/archive\/2009\/06\/11\/windows-event-log-in-powershell-part-ii.aspx\" target=\"_blank\">Get-WinEvent cmdlet<\/a>. (Note: Windows PowerShell is built into Windows 7\/Server 2008 R2.&#160; You will have to install <a href=\"http:\/\/go.microsoft.com\/fwlink\/?LinkID=151321\" target=\"_blank\">PowerShell V2 on Windows Vista<\/a> to get this to work.)<\/p>\n<p>PowerShell makes it is easy to just for exactly what you need. For example, in the \u201cShort Answer\u201d above I just ask for the specific CHKDSK event ID 1001 from the \u201cMicrosoft-Windows-Wininit\u201d event provider:<\/p>\n<p><font color=\"#0000a0\" face=\"Courier New\">get-winevent -FilterHashTable @{logname=&quot;Application&quot;; id=&quot;1001&quot;}| ?{$_.providername \u2013match &quot;wininit&quot;} | fl timecreated, message<\/font><\/p>\n<p><strong>But how did you know where to find that!?     <br \/><\/strong>Truthfully, I really didn\u2019t. I had to dig. This is one of the reasons I use PowerShell. Sometimes I have to ask for everything and filter through to find what I want. In this case, I started with looking at absolutely everything that had happened since 7:00am today, which was the time of my last boot. I dumped this all to Out-GridView so I could see it easily.<\/p>\n<p><font color=\"#0000a0\" face=\"Courier New\">get-winevent -FilterHashTable @{logname=&quot;*&quot;; starttime=&quot;7:00am&quot;} | select timecreated,providername,id,containerlog,message | out-gridview<\/font><\/p>\n<p><a href=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/captureoutgridview1.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px\" title=\"Capture - OutGridView\" border=\"0\" alt=\"Capture - OutGridView\" src=\"https:\/\/kmwoley.com\/blog\/wp-content\/uploads\/2009\/11\/captureoutgridview-thumb1.jpg\" width=\"504\" height=\"345\" \/><\/a> <\/p>\n<p><em>(Note: that the \u2018starttime\u2019 can take all manner of date and time formats, e.g. 11\/25\/2009 would have worked as well. If you need to set an upper bound on the time, use \u2018endtime\u2019.)<\/em><\/p>\n<p>Next, I used Out-GridView to filter the results looking for the keyword \u201cCHKDSK\u201d in the Message field. This showed me who logged the event (Microsoft-Windows-Wininit) and what ID the event has (1001). From there, I created the query that is in the \u201cShort\u201d answer above.<\/p>\n<p><strong>What about other related events?     <br \/><\/strong>I was wondering the same thing. Probably the most useful query here is to search for the keyword \u201cDisk\u201d in Out-GridView which will show you several events of interest. It was interesting to see that there are also several events from NTFS, for example, which have indicated that the volume was corrupt in the first place. Also, I apparently have a few bad blocks on some of my disks I\u2019m gonna see about taking care of&#8230; <\/p>\n<p><strong>Alternatives     <br \/><\/strong>You can also see the same data in the Windows EventViewer, but I find it much harder to find things in there unless you know exactly what you\u2019re looking for. The Event Viewer can be found on Vista and Windows 7 by going to Start and then searching for \u201cEvent Viewer\u201d.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>My recent hard disk failure made me realize that I had no idea where to find the CHDSK logs that are created when Windows runs CHKDSK at boot. In my case, I had just installed a drive that had a bunch of NTFS corruptions caused by a different computer. Below I walk though what I &hellip; <a href=\"https:\/\/kmwoley.com\/blog\/where-to-find-chkdsk-results-in-vista-windows-7\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Where to find CHKDSK results in Vista, Windows 7<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[198,229,235,233,232,234,231,230,184,193],"class_list":["post-441","post","type-post","status-publish","format-standard","hentry","category-geek","tag-boot","tag-chkdsk","tag-disk","tag-event-log","tag-get-winevent","tag-hard-disk","tag-log","tag-results","tag-vista","tag-windows-7"],"_links":{"self":[{"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/posts\/441","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/comments?post=441"}],"version-history":[{"count":4,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/posts\/441\/revisions"}],"predecessor-version":[{"id":463,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/posts\/441\/revisions\/463"}],"wp:attachment":[{"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/media?parent=441"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/categories?post=441"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kmwoley.com\/blog\/wp-json\/wp\/v2\/tags?post=441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}