Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: Lady on September 05, 2015, 05:06:03 am
-
Hi y'all,
I partitioned the internal HD on my laptop and out of curiosity checked the partitions on my desktop. I noticed that the E: partition is divided into two. See screenshot. No idea how that came about as this was done for me in my pc shop when I bought the custom-made desktop.
Now I (think I) know how to get the two together using the Minitool Partition Wizard, but isn't it wise to get all the music files off of these two partitions before I embark on another Partition Adventure? :cheesy:
Or doesn't it make any difference and I can let this be?
-
Shoot I'm color blind to green and red but does the color legend match to Any form of raid and I would say yes always back up if you mess with partitions
-
That is odd that 2 E: partitions would show up. I also noticed that the other drivers are all basic MBR, as they should be, but the drive with D: and E: is dynamic.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa363785%28v=vs.85%29.aspx
I dont think it should have been set to dynamic.
Shane
-
Thank you, Shane, for pointing that out. Had no idea. That article though is WAY too difficult for me. I'll ask the head of the tech dept. of my pc shop why they did that and if he can help out to fix it. In the meantime I'll read some more on the subject and see if I can do it myself.
Can't I earn karma points by doing my darndest best to try to understand all this IT stuff and fix my pc problems? :cheesy: :cheesy: :cheesy:
-
Sorry lady I always hate color legends in bright colors or colors near the same tone.
-
I would love to tell you, Julian, about the colors of the legends but I didn't understand your post. What is it you need to know?
-
Hey, I just noticed I'm not a newbie anymore but a Jr. Member!!! I'm higher up the ladder. That's similar to earning karma points.
But I fooled you, guys. I'm just asking a LOT of questions. Hahaha.
-
Lol congrats!
Hey, I just noticed I'm not a newbie anymore but a Jr. Member!!! I'm higher up the ladder. That's similar to earning karma points.
But I fooled you, guys. I'm just asking a LOT of questions. Hahaha.
-
Julian, did you see my post before my last?
I just got an idea. I'm attaching two screenshots from the Windows Disk Management, which is in black and white mostly. It's in Dutch, so you have to be a little creative, haha. "Schijf" means Disk.
The only colors I see are on Disk 0, which is an olive-green, meaning basic volume (?, translating).
And Disk 1 and 6 and 7 are dark-blue, meaning primary partition.
Is that helpful?
-
Aaah that's a spanned dynamic disk meaning it looks like that may be a mirrored volume. Hmmmm but the same drive letter is confusing I've had that happen before when the mirror broke when I had a raid 1 setup but after I rebuilt the array it made it one drive letter again.
-
Alright Julian, that post of yours is just all Chinese to me..... :confused:
I read some about dynamic and basic disks but couldn't find what is actually the problem or risk of having dynamic disks. Can you tell me?
I have a bit of a problem with asking my friend, the head of the tech dept of my pc shop, to fix this because sometimes I get doubts about his expertise. I showed HIM a few tricks or solved something he couldn't. Minor stuff, of course, but still... I'm gonna test him with this new knowledge I have about the disks. :tongue: Just to say I'd rather do this myself. With you guys.
I found this piece of info. Do you think I could work with that? Because there are special programs for it but I read people having problems with them.
From: http://incisiveradar.com/how-to-convert-dynamic-disk-to-basic-disk/
Converting Dynamic disks to Basic Disks in Windows:
Before converting the dynamic disks into basic disks in Windows, I would recommend you to create a recovery media of your operating system and move the other important files into an external hard drive. Once you are ready, you can use the following steps to convert dynamic disks to basic disks.
Step 1: Open the Run dialog box by using the hot key combination Windows Logo Key + R
Step 2: In the Run dialog box type in diskmgmt.msc and hit enter.
Step 3: Now in the Disk Management window look for the dynamic disk you want to convert into a basic disk.
Step 4: Right click on each volume of the corresponding dynamic disk and click Delete Volume for each volume on the disk.
Step 5: When you have completed deleting all the volumes, right click on those disks and select Convert to Basic Disk.
Since my E: only contains music files I assume I don't run a real risk of getting into problems systemwise. Is that correct? It would be similar to making a new partition, wouldn't it? Just back up the files (which I already have, twice, on my 2 external HDDs), delete the volume, convert them to basic disks, paste the two E: disks together with Minitool and put the files back.
Piece of cake or what? :cheesy:
-
Julian, can you give me the green light to what I suggested? It's rather a scary thing to do, you know.
Maybe I should use Minitool instead of Windows Disk Management?
-
Julian, can you give me the green light to what I suggested? It's rather a scary thing to do, you know.
Maybe I should use Minitool instead of Windows Disk Management?
it is a scary thing to do I'm looking at d as well and it looks to be the same partition type as well I don't know why the partitions were setup that way best thing is to back up the hdd before messing with partitions . I just don't want you to delete the music drive and it messing with the d drive as well. I normally have a primary partition and have the folders redirected to another hdd I'll show you in a bit because I'm on my phone at the moment.
-
Before you put your energy in explaining your suggestion, let me try to get in touch with the head of the tech dept of my pc shop where I bought the custom-made desktop pc. I asked them to partition the internal HDD into C:, D: and E:. I'll ask him why they did that. I have no idea what your suggestion is like, sounds pretty far-out to me (sorry), but I prefer to get it all back to 3 basic partitions.
I always have all my data of D: and E: backed up at least twice, so nothing to worry there. So if deleting E: means interference with D:, that's okay, because D:'s volume has to be deleted as well for it to be turned into a basic disk too. So my idea was to delete both volumes of D: and E: and change them back into basis disks and add the data again. Wouldn't that work?
Actually, the longer I'm on this Partition Adventure (or Partition Expotition as Winnie the Pooh would have said, hahaha), the more I think it's gonna be a breeze. :cheesy: What's the worst that could happen? A total crash? C: won't be touched, so......Or am I being overconfident? :smiley:
And I still don't know what's so bad about having dynamic disks. All I read was that advanced users could do more things with them.
-
[Second post]
Hey! I got one karma point!!! My first! Yoohooo!
Errr.....how exactly did I get that?
-
Either Shane or Julian clicked on Applaud which gave you a Karma point for your perseverance or should that be persistence :)
I'll give you one as well because of the work you have put in :)
-
Okay, starting out on my second Partition Expotition! :cheesy:
This is what I am going to do.
In Minitool I will delete the volumes of D: and E:. (All data are backed-up.) Then I will use the option Convert Dynamic Disk to Basic. Then I must get the two parts of E: glued together again somehow. And finally I'll put the data back on.
Does that sound right to you guys?
I guess a system restore point is of no use here?
Interesting question: why doesn't my SSD-drive of 128 Gb show in Minitools with all the other HDs?
-
I may have clicked it..... karma baby!
Shane
-
Thanks, Shane! :cheesy:
Only positive karma from now on! :wink:
-
Can somebody approve my Partition Expotition Plan, so I won't get lost in the Hundred Terabyte Wood? :cheesy:
-
Guys, I just found out something which might pose more problems with the partitions.
In my desktop pc I have a 128 Gb SSD and a 2 Tb internal HD. The pc shop had made the partitions C:, D: and E:. You know, the dynamic discs. BTW, I spoke to the head of the tech dept. and he admitted there must have been made a mistake during installation. He said: "just change them back to standard discs, it's easy". Okay, the words "just" and "easy" I would not use.... :confused:
Two things (in my Obama voice which sounds nothing like him): :cheesy:
Recently I changed the volumes of the partitions around. I needed some more space on D: and E: and took that off of C:. I don't remember its volume before I decreased it. Still left quite enough on C: (capacity now 111 Gb, unused 46 Gb). Then somebody told me to not defragment C: as it was the SSD. I use Wise Disk Cleaner and have done the defragmentation of C:, D:, E:, F: and G, the last two being my two external HDs. Yesterday I downloaded O&O Defrag and that did give a warning message to not defrag C: as it was the SSD.
Question 1: did I make a mistake by defragmenting C: with Wise Disk Cleaner?
Question 2: isn't it true that it's impossible to move flash memory to D: and E: on the HD, as that is a different type of memory? So where did that go? And shouldn't I change it back to its original size of 128 Gb and stay clear of this whole SSD?
But......it gets even better (or worse): I don't remember the exact volumes before I changed them. But the weird thing is that I added at least 200 Gb to E: for my music files as E: tended to get filled up. The same with D:. I didn't just add a couple of Gbs to it, also more like 100 Gb. I do remember a large overcapacity of C:. And from 128 (SSD size) tot 111 Gb is only 17 Gb. That would mean that C: wasn't just comprised of the SSD alone but of HD memory too. Is that possible and normal?
Even weirder, but maybe an ignorant observation on my part: if you look at what data Speccy gives under Storage, the Kingston SSD: "speed: not used". To me that doesn't sound good, but maybe this is perfectly fine. Is it?
Speccy mentions the disk letters C: and F: and G: but not D: and E:. Is that normal?
http://speccy.piriform.com/results/ozuNekRLhA5gqgBTV1w61d1
These Speccy things might not be a problem at all. My main concern is the defragmentation and decreasing of volume of C: that I did and its possible impact on the SSD.
-
My dear guys, I'd like to say this.
Over the last few days I realized that the more I read about IT stuff and the deeper I dig into my PCs, the more questions I have, simply because I only have a very limited knowledge. It's not a good thing, it's becoming too much for me now. I feel I'm getting overwhelmed. There's always something new, you know. Although I find it highly interesting, it takes up too much of my time and energy and now of my well-being.
Forget about my last post. I guess it's all alright, otherwise my desktop would not be functioning, right? LOL
If someone can approve of my plan to fix the partitions, then that will be one major problem less. Please give me some reassurance I can do this. Such an Expotition is serious business, you know. :smiley:
-
Sorry I havent replied, for the last 3 weeks I have been on an insane programming session. I am just now getting back to the forums and have over 100+ threads to look over. So my brain is a little fried right now, but if you still are looking for an answer just hit me up Monday and I will be able to think better lol
Shane
-
Hi Shane,
I TOTALLY understand about fried brains. I had to distance myself from repairing my PCs for a while just now. Have cooled off again. Hope you have too. :)
I still would like to change the partitions to standard. I reread my posts and most questions are still valid for me, so if you would like to take the time to answer them, I'd be very pleased.
I got so confused about the volume on C:. I understand better now. When taking volume off of C: I had forgotten about the SSD part there and just happily went along, hahaha. Then when I remembered about the SSD I got scared I did something wrong and got totally confused. Then finally I thought about the Gibibyte thing. And I found this about an SSD of 128 Gb (as I have):
There have been some comments regarding the fact that this phenomenon has to be explained with the discrepancy between advertised space, stated in GigaBytes (e.g. 128x 10^9 Bytes) versus the GibiByte value the operating system shows, which is—most of the time—a power of two, calculating to 119.2 Gibibyte in this example. (...) While I certainly can’t state which exact algorithms need most of that extra space, the calculation stays the same. The manufacturer assembles an SSD that indeed uses a power of two number of flash cells (or a combination of such), though the controller does not make all that space visible to the operating system. The space that’s left is advertised as Gigabytes, netting you 111 Gibibyte in this example. (from: http://superuser.com/questions/747244/why-do-ssds-have-weird-sizes)
He mentions 111 Gibibyte!! That may mean that my PC itself indicated the 111 Gb as the lowest possible size I could play it down to. I don't remember as it's been a while. If this is true then my C: now is only comprised of the SSD. Would this be correct, Shane? Then I have no problem there at all. Pffff. Thank God the PC was smarter than me. This time then. Hahaha.
Please take your time with this. It has no real priority, although I'd like to get the desktop in perfect shape as well. Good news: my laptop is just SHINING from being so healthy! :cheesy: With a LOT of thanks to Boggin!
-
CAUTION;
What operating system are you using?
Why not, just back up all the data you have?
do a new clean install of your operating system and programs?
doing what your doing is quite messy, troublesome and can cause system failures that I have experienced!
Minitool from my experience is not safe to join together as your considering... if you have some operating files on them and join them, it will destroy your registry settings too...
is it better to have a clean system?
Regards
-
Hi Rick,
Thanks so much for responding. I am VERY cautious, that's why I was asking for consent from the forum.
As the changes will apply to disks D: and E: and I have all Windows operating files on C:, my logical thought was that nothing could hamper the operating system. On D: are my personal files and on E: my music files.
Do you still think it's dangerous? And do I understand correctly that you're suggesting a total re-installation? That's a LOT of work. :-S I could also do nothing at all. The desktop PC is functioning fine. I still don't know what the downsides of dynamic discs are.
What do you think?
Kind regards,
Lady
-
Oh, I forget to mention my operating system. I have Windows 7 Home Premium, Service Pack 1.
-
Rule number one;
if ain't broke, dont fix it!
-
as for new install, a lot of work today will solve a lot of time later!
Plus, keep you up to date with all the latest drivers from intell too :(
I find that intel is not supporting drivers for win7 now, that is a BIG problem in itself!
A clean reinstall now is best solution...
After re-install, there is one update need delete; I forgot whcih oneI found earlier, perhaps boggin remembers and can tell you?
it refers to WAT file, (interesting program to influence the public to upgrading to win10)
should be deleted off every system...
-
Shane, would you mind taking a look at this issue with the dynamic discs?
The desktop pc is functioning pretty okay. The only "problem" is that I often have to wait for it to process things before I can continue. Is that normal? And I'm rather scared of doing this operation. Can I just leave it? A re-installation is not an option. I have been working on this pc continually since I bought it two years ago and I really don't want to do another big operation.
However, I still wanted to do the Repair All In One, so I started just now by doing the sfc /scannow. It came up with errors. Is it useful to you guys that I upload the log or can I just continue with dism /online /cleanup-image /restorehealth?
Thanks, as always. :cheesy:
-
I'm not in a position to advise you with the dynamic disks but run the /restorehealth cmd to see what it reports then run the sfc /scannow again.
The /restorehealth cmd tends to hang at 20% but does eventually complete.
So as not to upload the complete CBS log for the sfc /scannow, if it still reports unable to repair all files then enter -
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt
The forum may allow you to copy & paste the cmd to the cmd prompt so as to avoid typos.
This will put an icon onto the Desktop which will open the CBS log in Notepad which you can copy & paste into the reply box and will display only what it could and couldn't repair.
-
I ran the restore health cmd and it says it doesn't recognize it. It does show a DISM log. Is it different on W7?
-
The /restorehealth cmd doesn't work on Win 7 and usually returns Error 87.
I assumed someone had advised you run that Dism cmd and that you were using the appropriate Windows version that accepts it.
Did you run the sfc scannow again to produce a current CBS log to post.
Sometimes if you don't run the findstr cmd straight after a sfc scannow, it may not pick up the current log.
-
Yes Boggin, that someone was you! :-D You taught me the scan and restorehealth cmds for my laptop (W8.1).
I did the scannow again and the findstr cmd. I got an sfcdetails log on my desktop. Is that the one you meant? It's rather large.
-
Oh, I see I didn't read the findstr cmd properly. It says sfcdetails.txt. :S But it doesn't say CBS but CSI.... That confused me.
Well, I guess it's alright then. Here's the log.
2015-11-03 10:36:19, Info CSI 00000009 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:19, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:19, Info CSI 0000000c [SR] Verify complete
2015-11-03 10:36:19, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:19, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:20, Info CSI 00000010 [SR] Verify complete
2015-11-03 10:36:20, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:20, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:20, Info CSI 00000014 [SR] Verify complete
2015-11-03 10:36:20, Info CSI 00000015 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:20, Info CSI 00000016 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:21, Info CSI 00000018 [SR] Verify complete
2015-11-03 10:36:21, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:21, Info CSI 0000001a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:21, Info CSI 0000001c [SR] Verify complete
2015-11-03 10:36:21, Info CSI 0000001d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:21, Info CSI 0000001e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:21, Info CSI 00000020 [SR] Verify complete
2015-11-03 10:36:22, Info CSI 00000021 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:22, Info CSI 00000022 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:22, Info CSI 00000024 [SR] Verify complete
2015-11-03 10:36:22, Info CSI 00000025 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:22, Info CSI 00000026 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:22, Info CSI 00000028 [SR] Verify complete
2015-11-03 10:36:22, Info CSI 00000029 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:22, Info CSI 0000002a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:23, Info CSI 0000002c [SR] Verify complete
2015-11-03 10:36:23, Info CSI 0000002d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:23, Info CSI 0000002e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:23, Info CSI 00000030 [SR] Verify complete
2015-11-03 10:36:23, Info CSI 00000031 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:23, Info CSI 00000032 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:23, Info CSI 00000034 [SR] Verify complete
2015-11-03 10:36:24, Info CSI 00000035 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:24, Info CSI 00000036 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:24, Info CSI 00000038 [SR] Verify complete
2015-11-03 10:36:24, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:24, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:24, Info CSI 0000003c [SR] Verify complete
2015-11-03 10:36:24, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:24, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:25, Info CSI 00000040 [SR] Verify complete
2015-11-03 10:36:25, Info CSI 00000041 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:25, Info CSI 00000042 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:25, Info CSI 00000044 [SR] Verify complete
2015-11-03 10:36:25, Info CSI 00000045 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:25, Info CSI 00000046 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:25, Info CSI 00000048 [SR] Verify complete
2015-11-03 10:36:26, Info CSI 00000049 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:26, Info CSI 0000004a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:26, Info CSI 0000004c [SR] Verify complete
2015-11-03 10:36:26, Info CSI 0000004d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:26, Info CSI 0000004e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:26, Info CSI 00000050 [SR] Verify complete
2015-11-03 10:36:26, Info CSI 00000051 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:26, Info CSI 00000052 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:27, Info CSI 00000054 [SR] Verify complete
2015-11-03 10:36:27, Info CSI 00000055 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:27, Info CSI 00000056 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:28, Info CSI 00000058 [SR] Verify complete
2015-11-03 10:36:28, Info CSI 00000059 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:28, Info CSI 0000005a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:28, Info CSI 0000005c [SR] Verify complete
2015-11-03 10:36:28, Info CSI 0000005d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:28, Info CSI 0000005e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:29, Info CSI 00000060 [SR] Verify complete
2015-11-03 10:36:29, Info CSI 00000061 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:29, Info CSI 00000062 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:29, Info CSI 00000064 [SR] Verify complete
2015-11-03 10:36:30, Info CSI 00000065 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:30, Info CSI 00000066 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:30, Info CSI 00000068 [SR] Verify complete
2015-11-03 10:36:30, Info CSI 00000069 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:30, Info CSI 0000006a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:30, Info CSI 0000006c [SR] Verify complete
2015-11-03 10:36:31, Info CSI 0000006d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:31, Info CSI 0000006e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:31, Info CSI 00000070 [SR] Verify complete
2015-11-03 10:36:31, Info CSI 00000071 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:31, Info CSI 00000072 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:31, Info CSI 00000074 [SR] Verify complete
2015-11-03 10:36:32, Info CSI 00000075 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:32, Info CSI 00000076 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:32, Info CSI 00000078 [SR] Verify complete
2015-11-03 10:36:32, Info CSI 00000079 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:32, Info CSI 0000007a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:32, Info CSI 0000007c [SR] Verify complete
2015-11-03 10:36:33, Info CSI 0000007d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:33, Info CSI 0000007e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:34, Info CSI 00000080 [SR] Verify complete
2015-11-03 10:36:34, Info CSI 00000081 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:34, Info CSI 00000082 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:35, Info CSI 00000084 [SR] Verify complete
2015-11-03 10:36:35, Info CSI 00000085 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:35, Info CSI 00000086 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:35, Info CSI 00000088 [SR] Verify complete
2015-11-03 10:36:36, Info CSI 00000089 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:36, Info CSI 0000008a [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:37, Info CSI 0000008c [SR] Verify complete
2015-11-03 10:36:37, Info CSI 0000008d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:37, Info CSI 0000008e [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:39, Info CSI 00000091 [SR] Verify complete
2015-11-03 10:36:39, Info CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:39, Info CSI 00000093 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:41, Info CSI 00000097 [SR] Verify complete
2015-11-03 10:36:41, Info CSI 00000098 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:41, Info CSI 00000099 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:42, Info CSI 0000009d [SR] Verify complete
2015-11-03 10:36:43, Info CSI 0000009e [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:43, Info CSI 0000009f [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:44, Info CSI 000000a1 [SR] Verify complete
2015-11-03 10:36:44, Info CSI 000000a2 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:44, Info CSI 000000a3 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:47, Info CSI 000000c5 [SR] Verify complete
2015-11-03 10:36:48, Info CSI 000000c6 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:48, Info CSI 000000c7 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:48, Info CSI 000000c8 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\APPLETS"\[l:24{12}]"IMJPCLST.DLL" from store
2015-11-03 10:36:48, Info CSI 000000c9 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\APPLETS"\[l:24{12}]"IMJPCLST.XML" from store
2015-11-03 10:36:49, Info CSI 000000ca [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPST.DIC" from store
2015-11-03 10:36:49, Info CSI 000000cb [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\APPLETS"\[l:22{11}]"IMJPCAC.DLL" from store
2015-11-03 10:36:49, Info CSI 000000cc [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:20{10}]"IMJPCD.DLL" from store
2015-11-03 10:36:49, Info CSI 000000cd [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"imjppdmg.exe" from store
2015-11-03 10:36:49, Info CSI 000000ce [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"IMJPTIP.DLL" from store
2015-11-03 10:36:49, Info CSI 000000d2 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"IMJPDADM.EXE" from store
2015-11-03 10:36:49, Info CSI 000000d3 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"IMJPDCTP.DLL" from store
2015-11-03 10:36:49, Info CSI 000000d4 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"IMJPUEX.EXE" from store
2015-11-03 10:36:49, Info CSI 000000d5 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"IMJPDCT.EXE" from store
2015-11-03 10:36:49, Info CSI 000000d6 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"imjpuexc.exe" from store
2015-11-03 10:36:49, Info CSI 000000d7 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPLN.DIC" from store
2015-11-03 10:36:49, Info CSI 000000d9 [SR] Verify complete
2015-11-03 10:36:50, Info CSI 000000da [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:50, Info CSI 000000db [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:50, Info CSI 000000dc [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"IMJPDSVR.EXE" from store
2015-11-03 10:36:50, Info CSI 000000dd [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPGN.GRM" from store
2015-11-03 10:36:50, Info CSI 000000de [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"IMJPMGR.EXE" from store
2015-11-03 10:36:51, Info CSI 000000df [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"imjpcus.dll" from store
2015-11-03 10:36:51, Info CSI 000000e0 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\applets"\[l:30{15}]"mshwjpnrIME.dll" from store
2015-11-03 10:36:51, Info CSI 000000e1 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:22{11}]"IMJPAPI.DLL" from store
2015-11-03 10:36:51, Info CSI 000000e2 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\APPLETS"\[l:22{11}]"IMJPSKF.DLL" from store
2015-11-03 10:36:51, Info CSI 000000e3 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPCH.DIC" from store
2015-11-03 10:36:51, Info CSI 000000e4 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMEJP10\APPLETS"\[l:24{12}]"IMJPKDIC.DLL" from store
2015-11-03 10:36:51, Info CSI 000000e5 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:24{12}]"JPNPADEN.CHM" from store
2015-11-03 10:36:51, Info CSI 000000e6 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPTU.CHM" from store
2015-11-03 10:36:51, Info CSI 000000e7 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPPD.CHM" from store
2015-11-03 10:36:51, Info CSI 000000e8 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPDT.CHM" from store
2015-11-03 10:36:51, Info CSI 000000e9 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:20{10}]"IMJPCL.CHM" from store
2015-11-03 10:36:51, Info CSI 000000ea [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:22{11}]"IMJPDTE.CHM" from store
2015-11-03 10:36:51, Info CSI 000000eb [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMEJP10\HELP"\[l:22{11}]"IMJPCLE.CHM" from store
2015-11-03 10:36:51, Info CSI 000000ec [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"imjptk.dic" from store
2015-11-03 10:36:51, Info CSI 000000ed [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMEJP10"\[l:24{12}]"imjputyc.dll" from store
2015-11-03 10:36:52, Info CSI 000000ef [SR] Verify complete
2015-11-03 10:36:52, Info CSI 000000f0 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:52, Info CSI 000000f1 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:53, Info CSI 000000f2 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPSB.DIC" from store
2015-11-03 10:36:53, Info CSI 000000f3 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMEJP10\DICTS"\[l:20{10}]"IMJPNM.DIC" from store
2015-11-03 10:36:53, Info CSI 000000f5 [SR] Verify complete
2015-11-03 10:36:53, Info CSI 000000f6 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:53, Info CSI 000000f7 [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:55, Info CSI 000000f9 [SR] Verify complete
2015-11-03 10:36:55, Info CSI 000000fa [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:55, Info CSI 000000fb [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:57, Info CSI 000000fd [SR] Verify complete
2015-11-03 10:36:57, Info CSI 000000fe [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:57, Info CSI 000000ff [SR] Beginning Verify and Repair transaction
2015-11-03 10:36:58, Info CSI 00000100 [SR] Cannot repair member file [l:22{11}]"desktop.ini" of Microsoft-Windows-ehome-samplemedia, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:36:58, Info CSI 00000101 [SR] Cannot repair member file [l:58{29}]"win7_scenic-demoshort_raw.wtv" of Microsoft-Windows-ehome-samplemedia, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:36:58, Info CSI 00000102 [SR] Cannot repair member file [l:22{11}]"desktop.ini" of Microsoft-Windows-ehome-samplemedia, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:36:58, Info CSI 00000103 [SR] This component was referenced by [l:176{88}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MediaCenter"
2015-11-03 10:36:58, Info CSI 00000104 [SR] Cannot repair member file [l:58{29}]"win7_scenic-demoshort_raw.wtv" of Microsoft-Windows-ehome-samplemedia, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:36:58, Info CSI 00000105 [SR] This component was referenced by [l:176{88}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MediaCenter"
2015-11-03 10:36:59, Info CSI 00000107 [SR] Verify complete
2015-11-03 10:36:59, Info CSI 00000108 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:36:59, Info CSI 00000109 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:02, Info CSI 0000012c [SR] Verify complete
2015-11-03 10:37:02, Info CSI 0000012d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:02, Info CSI 0000012e [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:04, Info CSI 00000130 [SR] Verify complete
2015-11-03 10:37:05, Info CSI 00000131 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:05, Info CSI 00000132 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:10, Info CSI 00000134 [SR] Verify complete
2015-11-03 10:37:10, Info CSI 00000135 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:10, Info CSI 00000136 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:13, Info CSI 0000013a [SR] Verify complete
2015-11-03 10:37:13, Info CSI 0000013b [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:13, Info CSI 0000013c [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:14, Info CSI 0000013e [SR] Verify complete
2015-11-03 10:37:14, Info CSI 0000013f [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:14, Info CSI 00000140 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:15, Info CSI 00000142 [SR] Verify complete
2015-11-03 10:37:15, Info CSI 00000143 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:15, Info CSI 00000144 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:16, Info CSI 00000145 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMETC10"\[l:22{11}]"IMTCTIP.dll" from store
2015-11-03 10:37:17, Info CSI 00000146 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGT.IMD" from store
2015-11-03 10:37:17, Info CSI 00000147 [SR] Repairing corrupted file [ml:520{260},l:84{42}]"\??\C:\Windows\System32\IME\IMESC5\Applets"\[l:24{12}]"PINTLCSA.dll" from store
2015-11-03 10:37:17, Info CSI 00000148 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\IME\IMESC5\HELP"\[l:24{12}]"PINTLPAD.CHM" from store
2015-11-03 10:37:17, Info CSI 00000149 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\IME\IMESC5\HELP"\[l:24{12}]"PINTLPAE.CHM" from store
2015-11-03 10:37:17, Info CSI 0000014a [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:22{11}]"IMSCTIP.dll" from store
2015-11-03 10:37:18, Info CSI 0000014c [SR] Verify complete
2015-11-03 10:37:18, Info CSI 0000014d [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:18, Info CSI 0000014e [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:20, Info CSI 0000015c [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:18{9}]"IMTCV.IMD" from store
2015-11-03 10:37:21, Info CSI 00000160 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGVR.IMD" from store
2015-11-03 10:37:21, Info CSI 00000162 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:22{11}]"IMTCSKF.dll" from store
2015-11-03 10:37:21, Info CSI 00000163 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:22{11}]"IMTCDIC.dll" from store
2015-11-03 10:37:21, Info CSI 00000164 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:22{11}]"IMTCCAC.dll" from store
2015-11-03 10:37:21, Info CSI 00000165 [SR] Repairing corrupted file [ml:520{260},l:86{43}]"\??\C:\Windows\System32\IME\IMETC10\Applets"\[l:30{15}]"MSHWCHTRIME.dll" from store
2015-11-03 10:37:21, Info CSI 00000167 [SR] Verify complete
2015-11-03 10:37:21, Info CSI 00000168 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:21, Info CSI 00000169 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:22, Info CSI 0000016b [SR] Verify complete
2015-11-03 10:37:22, Info CSI 0000016c [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:22, Info CSI 0000016d [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:23, Info CSI 0000016e [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGID.IMD" from store
2015-11-03 10:37:23, Info CSI 0000016f [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGDM.IMD" from store
2015-11-03 10:37:23, Info CSI 00000170 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:24{12}]"PMIGRATE.dll" from store
2015-11-03 10:37:23, Info CSI 00000171 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGR.IMD" from store
2015-11-03 10:37:23, Info CSI 00000172 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGL.IMD" from store
2015-11-03 10:37:23, Info CSI 00000173 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGJ.IMD" from store
2015-11-03 10:37:23, Info CSI 00000174 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGI.IMD" from store
2015-11-03 10:37:23, Info CSI 00000175 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGD.IMD" from store
2015-11-03 10:37:23, Info CSI 00000176 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGC.IMD" from store
2015-11-03 10:37:23, Info CSI 00000177 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD" from store
2015-11-03 10:37:23, Info CSI 00000178 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\IME\IMESC5\HELP"\[l:24{12}]"PINTLGNE.CHM" from store
2015-11-03 10:37:23, Info CSI 00000179 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\IME\IMESC5\HELP"\[l:24{12}]"PINTLGNT.CHM" from store
2015-11-03 10:37:23, Info CSI 0000017a [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGIX.IMD" from store
2015-11-03 10:37:23, Info CSI 0000017b [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGCF.IMD" from store
2015-11-03 10:37:23, Info CSI 0000017c [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGDX.IMD" from store
2015-11-03 10:37:23, Info CSI 0000017d [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGAB.IMD" from store
2015-11-03 10:37:23, Info CSI 0000017e [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGAP.IMD" from store
2015-11-03 10:37:23, Info CSI 0000017f [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:24{12}]"PINTLGAS.IMD" from store
2015-11-03 10:37:23, Info CSI 00000180 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:20{10}]"imscui.DLL" from store
2015-11-03 10:37:23, Info CSI 00000181 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:22{11}]"ImSCCfg.DLL" from store
2015-11-03 10:37:23, Info CSI 00000182 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:24{12}]"IMSCPROP.exe" from store
2015-11-03 10:37:23, Info CSI 00000183 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\IME\IMESC5"\[l:24{12}]"ImSCCore.dll" from store
2015-11-03 10:37:23, Info CSI 00000185 [SR] Verify complete
2015-11-03 10:37:23, Info CSI 00000186 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:23, Info CSI 00000187 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:24, Info CSI 00000189 [SR] Verify complete
2015-11-03 10:37:24, Info CSI 0000018a [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:24, Info CSI 0000018b [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:25, Info CSI 0000018c [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMETC10"\[l:20{10}]"imtcui.DLL" from store
2015-11-03 10:37:25, Info CSI 0000018d [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMETC10\HELP"\[l:20{10}]"IMTCTC.CHM" from store
2015-11-03 10:37:25, Info CSI 0000018e [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:20{10}]"IMTCPH.IMD" from store
2015-11-03 10:37:25, Info CSI 0000018f [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:20{10}]"IMTCLS.IMD" from store
2015-11-03 10:37:25, Info CSI 00000190 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:18{9}]"IMTCL.IMD" from store
2015-11-03 10:37:25, Info CSI 00000191 [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMETC10\HELP"\[l:20{10}]"IMTCEN.CHM" from store
2015-11-03 10:37:25, Info CSI 00000192 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMETC10"\[l:22{11}]"IMTCCFG.DLL" from store
2015-11-03 10:37:25, Info CSI 00000193 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:20{10}]"IMTCCJ.IMD" from store
2015-11-03 10:37:25, Info CSI 00000194 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:24{12}]"IMTCPHCS.IMD" from store
2015-11-03 10:37:25, Info CSI 00000195 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMETC10"\[l:24{12}]"IMTCPROP.exe" from store
2015-11-03 10:37:25, Info CSI 00000196 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:24{12}]"IMTCCJCS.IMD" from store
2015-11-03 10:37:25, Info CSI 00000197 [SR] Repairing corrupted file [ml:520{260},l:70{35}]"\??\C:\Windows\System32\IME\IMETC10"\[l:24{12}]"IMTCCORE.DLL" from store
2015-11-03 10:37:26, Info CSI 00000198 [SR] Repairing corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:18{9}]"IMTCS.IMD" from store
2015-11-03 10:37:26, Info CSI 0000019b [SR] Verify complete
2015-11-03 10:37:26, Info CSI 0000019c [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:26, Info CSI 0000019d [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:28, Info CSI 0000019e [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\ime\imekr8"\[l:22{11}]"imkrapi.dll" from store
2015-11-03 10:37:29, Info CSI 0000019f [SR] Repairing corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\ime\imekr8\dicts"\[l:22{11}]"imkrhjd.lex" from store
2015-11-03 10:37:29, Info CSI 000001a0 [SR] Repairing corrupted file [ml:520{260},l:80{40}]"\??\C:\Windows\System32\ime\imekr8\dicts"\[l:22{11}]"imkrhjd.dll" from store
2015-11-03 10:37:29, Info CSI 000001a1 [SR] Repairing corrupted file [ml:520{260},l:84{42}]"\??\C:\Windows\System32\ime\imekr8\applets"\[l:22{11}]"imkrcac.dll" from store
2015-11-03 10:37:30, Info CSI 000001a4 [SR] Verify complete
2015-11-03 10:37:30, Info CSI 000001a5 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:30, Info CSI 000001a6 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:31, Info CSI 000001a7 [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\ime\imekr8"\[l:22{11}]"imkrudt.dll" from store
2015-11-03 10:37:31, Info CSI 000001a8 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\ime\imekr8\help"\[l:20{10}]"imkrpd.chm" from store
2015-11-03 10:37:31, Info CSI 000001a9 [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\ime\imekr8\help"\[l:20{10}]"imkren.chm" from store
2015-11-03 10:37:31, Info CSI 000001aa [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\ime\imekr8\help"\[l:16{8}]"imkr.chm" from store
2015-11-03 10:37:31, Info CSI 000001ab [SR] Repairing corrupted file [ml:520{260},l:60{30}]"\??\C:\Windows\ime\imekr8\help"\[l:24{12}]"imkrpden.chm" from store
2015-11-03 10:37:31, Info CSI 000001ac [SR] Repairing corrupted file [ml:520{260},l:84{42}]"\??\C:\Windows\System32\ime\imekr8\applets"\[l:30{15}]"mshwkorrIME.dll" from store
2015-11-03 10:37:31, Info CSI 000001ad [SR] Repairing corrupted file [ml:520{260},l:84{42}]"\??\C:\Windows\System32\ime\imekr8\applets"\[l:22{11}]"imkrskf.dll" from store
2015-11-03 10:37:31, Info CSI 000001ae [SR] Repairing corrupted file [ml:520{260},l:68{34}]"\??\C:\Windows\System32\ime\imekr8"\[l:22{11}]"imkrtip.dll" from store
2015-11-03 10:37:31, Info CSI 000001b0 [SR] Verify complete
2015-11-03 10:37:32, Info CSI 000001b1 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:32, Info CSI 000001b2 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:32, Info CSI 000001b4 [SR] Verify complete
2015-11-03 10:37:33, Info CSI 000001b5 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:33, Info CSI 000001b6 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:35, Info CSI 000001b8 [SR] Verify complete
2015-11-03 10:37:35, Info CSI 000001b9 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:35, Info CSI 000001ba [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:37, Info CSI 000001bc [SR] Verify complete
2015-11-03 10:37:37, Info CSI 000001bd [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:37, Info CSI 000001be [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:39, Info CSI 000001c0 [SR] Verify complete
2015-11-03 10:37:39, Info CSI 000001c1 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:39, Info CSI 000001c2 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:44, Info CSI 000001d9 [SR] Verify complete
2015-11-03 10:37:44, Info CSI 000001da [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:44, Info CSI 000001db [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:45, Info CSI 000001dc [SR] Cannot repair member file [l:22{11}]"Kalimba.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001dd [SR] Cannot repair member file [l:22{11}]"desktop.ini" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001de [SR] Cannot repair member file [l:58{29}]"Maid with the Flaxen Hair.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001df [SR] Cannot repair member file [l:28{14}]"Sleep Away.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001e0 [SR] Cannot repair member file [l:22{11}]"Kalimba.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001e1 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2015-11-03 10:37:45, Info CSI 000001e2 [SR] Cannot repair member file [l:22{11}]"desktop.ini" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001e3 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2015-11-03 10:37:45, Info CSI 000001e4 [SR] Cannot repair member file [l:58{29}]"Maid with the Flaxen Hair.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001e5 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2015-11-03 10:37:45, Info CSI 000001e6 [SR] Cannot repair member file [l:28{14}]"Sleep Away.mp3" of Microsoft-Windows-MusicSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:37:45, Info CSI 000001e7 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2015-11-03 10:37:46, Info CSI 000001ea [SR] Verify complete
2015-11-03 10:37:46, Info CSI 000001eb [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:46, Info CSI 000001ec [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:53, Info CSI 000001ee [SR] Verify complete
2015-11-03 10:37:53, Info CSI 000001ef [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:53, Info CSI 000001f0 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:56, Info CSI 000001f2 [SR] Verify complete
2015-11-03 10:37:56, Info CSI 000001f3 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:56, Info CSI 000001f4 [SR] Beginning Verify and Repair transaction
2015-11-03 10:37:59, Info CSI 000001f6 [SR] Verify complete
2015-11-03 10:37:59, Info CSI 000001f7 [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:37:59, Info CSI 000001f8 [SR] Beginning Verify and Repair transaction
2015-11-03 10:38:01, Info CSI 000001fa [SR] Verify complete
2015-11-03 10:38:02, Info CSI 000001fb [SR] Verifying 100 (0x0000000000000064) components
2015-11-03 10:38:02, Info CSI 000001fc [SR] Beginning Verify and Repair transaction
2015-11-03 10:38:02, Info CSI 000001fd [SR] Cannot repair member file [l:18{9}]"Koala.jpg" of Microsoft-Windows-PhotoSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:38:02, Info CSI 000001fe [SR] Cannot repair member file [l:26{13}]"Jellyfish.jpg" of Microsoft-Windows-PhotoSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:38:02, Info CSI 000001ff [SR] Cannot repair member file [l:26{13}]"SampleRes.dll" of Microsoft-Windows-PhotoSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 10:38:02, Info &
-
I missed your Reply #26 which said you were using Win 7 - Sorry :)
The Dism repair cmds only work on the Win 8s and Win 10 else you're looking at a sfc /scannow or chkdsk /f or chkdsk /r
It looks like it's really screwed up.
Run a chkdsk /r to see if it reports any KBs in bad sectors on the HDD.
You can view its log in Event Viewer by going Start - type eventvwr and press enter.
When it has read the data, expand Windows Logs then click on Application/Action/Find then type chkdsk or wininit into the Find box and press enter.
Cancel the Find box and read the report in the scrollable window.
If you want to post the report, click on Copy/Copy details as text in the lower right pane then right click in the Reply box and select Paste.
-
Shane, would you mind taking a look at this issue with the dynamic discs?
Sorry, with so many posts to catch up on I have gotten to the point that I trust what Boggin and Julian are doing and so when I see them helping someone I just move on and if they cant solve it they get a hold of me and I see if I can help :-)
I have to head off in 5 min as I have multiple jobs and customers to go to in the morning and I have to wake up at 6:30, take the kids to school and then head off to the jobs.
I will have to do some research on the problem you are having to make sure I have the right info, so much going on right now I dont want to risk getting the wrong info, when it comes to the disks and the file system I dont like to take any chances.
Shane
-
Shane, no problem, I understand. It might not be an issue anymore, since I believe I'm fast approaching a re-installation now. :S
Boggin, here the log. It's in Dutch though. Tell me what I should do if you cannot make it out.
Logboeknaam: Application
Bron: Microsoft-Windows-Wininit
Datum: 4-11-2015 9:00:16
Gebeurtenis-id:1001
Taakcategorie: Geen
Niveau: Informatie
Trefwoorden: Klassiek
Gebruiker: n.v.t.
Computer: User-PC
Beschrijving:
Het bestandssysteem op C: wordt gecontroleerd...
Het type bestandssysteem is NTFS.
Er is in een eerder stadium een schijfcontrole gepland.
Windows zal de schijf nu controleren.
Bestanden controleren (stap 1 van 5)...
Instantielabels voor het bestand 0x8e1a verwijderen.
Instantielabels voor het bestand 0xb5d5 verwijderen.
211456 bestandsrecords verwerkt.
De bestandscontrole is voltooid.
Indexvermeldingen die verwijzen naar bestand 48351 zullen niet worden
gevalideerd omdat dit bestand te veel bestandsnamen bevat.
Indexvermeldingen die verwijzen naar bestand 49333 zullen niet worden
gevalideerd omdat dit bestand te veel bestandsnamen bevat.
1891 records met grote bestanden verwerkt.
0 records met beschadigde bestanden verwerkt.
0 EA-records verwerkt.
10047 reparserecords verwerkt.
Indices controleren (stap 2 van 5)...
284516 indexvermeldingen verwerkt.
De indexcontrole voltooid.
0 niet-geïndexeerde bestanden gecontroleerd.
0 niet-geïndexeerde bestanden hersteld.
CHKDSK controleert de security descriptors (stap 3 van 5)...
211456 bestands-SD's/-SID's verwerkt.
1980 ongebruikte indexingangen in de index $SII
van het bestand 0x9 verwijderen.
1980 ongebruikte indexingangen in de index $SDH
van het bestand 0x9 verwijderen.
1980 ongebruikte security descriptors verwijderen.
De controle van security descriptors is voltooid.
36531 gegevensbestanden verwerkt.
Het USN-logboek controleren...
36774360 USN-bytes verwerkt.
Controle van USN-logboek is voltooid.
CHKDSK controleert de bestandsgegevens (stap 4 van 5)...
211440 bestanden verwerkt.
De controle van bestandsgegevens is voltooid.
Vrije ruimte controleren (stap 5 van 5)...
11225565 vrije clusters verwerkt.
De controle op vrije schijfruimte is voltooid.
Het bestandssysteem is hersteld.
117115903 kB totale schijfruimte.
71784860 kB in 164021 bestanden.
109108 kB in 36532 indexen.
0 kB in beschadigde sectoren.
319675 kB in gebruik door het systeem.
Het logboekbestand neemt 65536 kB in beslag.
44902260 kB beschikbaar op schijf.
4096 bytes per cluster
29278975 clusters in totaal op schijf
11225565 clusters beschikbaar op schijf
Interne info:
00 3a 03 00 74 0f 03 00 f3 ca 05 00 00 00 00 00 .:..t...........
c2 01 00 00 3f 27 00 00 00 00 00 00 00 00 00 00 ....?'..........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
De schijfcontrole is voltooid.
Een ogenblik geduld. De computer wordt opnieuw opgestart.
Gebeurtenis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-11-04T08:00:16.000000000Z" />
<EventRecordID>188309</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>User-PC</Computer>
<Security />
</System>
<EventData>
<Data>
Het bestandssysteem op C: wordt gecontroleerd...
Het type bestandssysteem is NTFS.
Er is in een eerder stadium een schijfcontrole gepland.
Windows zal de schijf nu controleren.
Bestanden controleren (stap 1 van 5)...
Instantielabels voor het bestand 0x8e1a verwijderen.
Instantielabels voor het bestand 0xb5d5 verwijderen.
211456 bestandsrecords verwerkt.
De bestandscontrole is voltooid.
Indexvermeldingen die verwijzen naar bestand 48351 zullen niet worden
gevalideerd omdat dit bestand te veel bestandsnamen bevat.
Indexvermeldingen die verwijzen naar bestand 49333 zullen niet worden
gevalideerd omdat dit bestand te veel bestandsnamen bevat.
1891 records met grote bestanden verwerkt.
0 records met beschadigde bestanden verwerkt.
0 EA-records verwerkt.
10047 reparserecords verwerkt.
Indices controleren (stap 2 van 5)...
284516 indexvermeldingen verwerkt.
De indexcontrole voltooid.
0 niet-geïndexeerde bestanden gecontroleerd.
0 niet-geïndexeerde bestanden hersteld.
CHKDSK controleert de security descriptors (stap 3 van 5)...
211456 bestands-SD's/-SID's verwerkt.
1980 ongebruikte indexingangen in de index $SII
van het bestand 0x9 verwijderen.
1980 ongebruikte indexingangen in de index $SDH
van het bestand 0x9 verwijderen.
1980 ongebruikte security descriptors verwijderen.
De controle van security descriptors is voltooid.
36531 gegevensbestanden verwerkt.
Het USN-logboek controleren...
36774360 USN-bytes verwerkt.
Controle van USN-logboek is voltooid.
CHKDSK controleert de bestandsgegevens (stap 4 van 5)...
211440 bestanden verwerkt.
De controle van bestandsgegevens is voltooid.
Vrije ruimte controleren (stap 5 van 5)...
11225565 vrije clusters verwerkt.
De controle op vrije schijfruimte is voltooid.
Het bestandssysteem is hersteld.
117115903 kB totale schijfruimte.
71784860 kB in 164021 bestanden.
109108 kB in 36532 indexen.
0 kB in beschadigde sectoren.
319675 kB in gebruik door het systeem.
Het logboekbestand neemt 65536 kB in beslag.
44902260 kB beschikbaar op schijf.
4096 bytes per cluster
29278975 clusters in totaal op schijf
11225565 clusters beschikbaar op schijf
Interne info:
00 3a 03 00 74 0f 03 00 f3 ca 05 00 00 00 00 00 .:..t...........
c2 01 00 00 3f 27 00 00 00 00 00 00 00 00 00 00 ....?'..........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
De schijfcontrole is voltooid.
Een ogenblik geduld. De computer wordt opnieuw opgestart.
</Data>
</EventData>
</Event>
-
I was able to use Translate with Bing to see that it had deleted some files of which I have no knowledge, but it will have known what it was doing.
My first instinct when I saw the sfc CBS log was to factory reset but given the type of corruption to pre-installed items, thought it prudent to run a check on the condition of the HDD.
I didn't need Translate with Bing to see that it reported 0 KB in bad sectors, so I would say that your free to go ahead with either a factory reset or reinstall.
You say that you have been trouble shooting this system for the last two years - had you run any "tune up" programs or registry cleaners on it in its earlier days ?
-
No, I never used such programmes. I know they can be doing more harm than good. It was just going wrong from the start.
I was on a Dutch forum then and I just reread part of my posts to recall what happened. After buying it in Dec. 2013 it malfunctioned and I had it re-installed by the pc shop after a few weeks. After that I got blue screens. especially on shutting down, and Firefox crashing. I also had screens opening and closing really slowly, very weird. I replaced one external HD that was constantly making a running noise. I also replaced a USB hub. In the Windows logs it gave (and still does, I just checked) a daily error that the last shutdown had happended unexpectedly, which is untrue and odd, but I was told to ignore that. The pc hung on updating, it didn't recognize my MP3-players and printer, programmes didn't respond and were shut down. All kinds of errors. It drove me crazy. I was on a Dutch forum then and we tried everything in the book. Just before another re-installation someone came up with Windows Repair All In One and all returned to normal. The only thing was that my dictionaries didn't function anymore, I thought it was due to the Repair but it turned out that these files had also been corrupted which showed after the Repair. No problem, I re-installed those.
So I thought everything was fine, until now. In the meantime I wrestled with my laptop as you very well know. Can I just ask you, Boggin? Yesterday I was on my laptop, deleting files and copying new versions of the files from a USB stick onto the laptop and all of a sudden the mouse led a life on its own and it looked like the laptop got all crazy for half a minute, changing the layout of Windows Explorer. Then it stopped. A few files were moved about. What was that?? Is that normal? I thought it was in tiptop shape? :(
Back to the desktop. Maybe, after careful consideration of this whole journey and summoning up my courage it's best to re-install and get it right from the start. I assume this pc shop made mistakes when installing. I know they work with apprentices. I mean, somebody has to have made those dynamic discs. Or can it in any way be due to the hardware, I mean the computer, the processor or something? I have a Hewlett Packard Pavillion p7-1423w, CPU Intel Core i5, SSD 128 Gb, internal HD 2 Tb. It's just plain crazy so many problems I've had with this desktop. But re-installing.... You have to know that I use a bunch of programmes and I am very particular about all the settings, so that's a LOT of work.
Do you agree that we'd better stop repairing? Would a proper re-installation solve everything then and give me back my peace? Or is this still repairable? What exactly is wrong, can you tell me?
I'm sorry, it has become lengthy. But now you know better about this pc and all the effort that I already put into it.
Sigh....
-
Those sample music and picture files that are showing as corrupt in the CBS log, I have those on my Toshiba pre-installed Win 7 but wouldn't have thought you would get them with a clean install of Win 7 done by a shop, unless it was an OEM install which is a cheaper method of installing Win 7.
While an offboot sfc /scannow can repair system files, I don't think it would be able to repair those sample files.
Where did you get the Win 7 install disk from ?
-
I read the log five times now but where are those sample files?? And are they that serious to have to re-install? I don't understand.
I bought a W7 licence in the pc shop when I bought the pc and got an official cd-rom. After the re-installation I got a copy cd-rom back. I protested, wanted the original, but they said it didn't matter at all.
-
They are time stamped 10:36:58 and then 10:37:45.
When you open Windows Explorer you will see the Music, Pictures and Videos Libraries and you may remember the samples that are in there.
You may recognise the sample music titles of Kalimba and Maid with the flaxen hair.
Go into the Music folder and see if they'll play.
You could most probably delete them but I don't know what has happened that has corrupted them.
Run SFCFix.exe and post that report which will be condensed to the CBS log.
http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/
If there's nothing seriously wrong with the rest of the system then you could just ignore them, unless Shane has any comment about them as he said he'll be back regarding the dynamic disks.
It's just that when I see something amiss with what I know to be preinstalled, I would have factory reset my machine.
I wouldn't have thought they would be entitled to keep a copy of your Win 7 disk, never mind the original.
-
Oh, you were referring to the previous log... :S I see.
All the sample pictures, videos and music I deleted long ago, so I cannot open them. How can such innocent files - in my view - be disruptive to the system if they're missing?
SFCFix.exe is not being recognized in the cmd prompt.
I must ask the pc shop whether any software was factory installed if I want to maybe do a factory reset.
I'm SO glad you don't agree with the copy I got back. I will try to get the original again, although it has been 1,5 years or so. Copies are regular practice. They say: "with your licence key you have the original". And: "cd-roms aren't given out anymore, you can download the software with your licence key". That's why I accepted that. I just wanted a cd-rom for easy re-installation in case I didn't have access to the internet.
Yes, it would be nice if Shane could find the time to look at this. But it's quite a long thread and, like he said, he has to put time into it to not make mistakes. What I'd like is that he just looks at how bad the status of my pc is and recommend continuing with the repair or a re-installation. So we can wait, cannot we? :smiley: Then I'll also have some more time to build my courage for the inevitable. :cheesy:
Oh, lightbulb moment: would a Windows Repair not put those files back?
-
Sorry - SFCFix.exe is a 3rd party program and I forgot to paste the link.
http://thetechcookbook.com/automatic-sfc-corruption-repair-sfcfix-exe/
There may be remnants in the registry which may cause sfc to try and repair the missing bits that you deleted, so if nothing else is untoward then you can probably ignore them.
-
Here is the SFCFix log. It repaired 16 files, that leaves 10 corrupted files. They all seem to be samples. Strange that the W7 cd-rom didn't have those, don't you think? If I may say so, I think it's pretty weird that these sample files have such an effect on the scans. So what to do next? Is there a place where we can find those 10 files? Is it an idea to ask someone who has W7 to find those files and send them to me? Or we can leave it.....
I assume you're pretty busy as well, but if possible, could you please comment on the paragraph (3rd) about my laptop in my message #38? Can these things happen and pose no problem? Like a hiccup? :cheesy:
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-11-09 14:47:29.762
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_1080_5sec_10mbps_h264.mp4 has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_1080_5sec_MPEG2_HD_15mbps.mpg has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_1080_5sec_MPEG2_HD_15mbps.mpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_1080_5sec_VC1_15mbps.wmv has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_480i_5sec_6mbps_new.mpg has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_480i_5sec_6mbps_new.mpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_480p_5sec_6mbps_new.mpg has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_480p_5sec_6mbps_new.mpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\Clip_480_5sec_6mbps_h264.mp4 has been successfully repaired from C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\winsat.wmv has been successfully repaired from C:\Windows\Performance\WinSAT\winsat.wmv.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\winsatencode.wmv has been successfully repaired from C:\Windows\Performance\WinSAT\winsatencode.wmv.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Hydrangeas.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Hydrangeas.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Jellyfish.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Jellyfish.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Koala.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Koala.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Lighthouse.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Lighthouse.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Penguins.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Penguins.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Tulips.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Tulips.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Chrysanthemum.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Chrysanthemum.jpg.
FIXED: Corruption at C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\Desert.jpg has been successfully repaired from D:\Mijn afbeeldingen 2\Desert.jpg.
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-ehome-samplemedia_31bf3856ad364e35_6.1.7600.16385_none_b6b9b223710b3802\desktop.ini
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-ehome-samplemedia_31bf3856ad364e35_6.1.7600.16385_none_b6b9b223710b3802\win7_scenic-demoshort_raw.wtv
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b\Kalimba.mp3
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b\desktop.ini
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b\Maid with the Flaxen Hair.mp3
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b\Sleep Away.mp3
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\SampleRes.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be\desktop.ini
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd\desktop.ini
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd\Wildlife.wmv
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 26
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 16
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-11-09 15:02:02.384
----------------------EOF-----------------------
-
While you deleted those sample files, there may be some residue in the registry for Windows still to be looking for them.
I don't normally advocate using a registry cleaner, but CCleaner's is one of the safest as it doesn't indiscriminately remove items that could damage your system and you can use the free version.
https://www.piriform.com/ccleaner/download
In Options click on Monitoring and uncheck the top and bottom buttons as there's no need for this.
Before I started using IOBit Uninstaller I use to use CCleaner's registry cleaner to clean out the residue after uninstalling programs and I'm still here :) so you can trust it.
However, I uncheck the box for ActiveX Issues before running the scan/clean.
Run another sfc /scannow afterwards to see if it still snags those, but if you aren't experiencing problems, then I suppose you could ignore the sfc report.
As for those Dynamic discs, I'll contact Shane to remind him he was going to research those and hopefully he will be able to get some time to get back to you, so don't do any reinstalling just yet.
-
Can I ask you again to say something about the laptop hiccup?
-
Can you put in a reminder about that so Shane will see it as he doesn't have time to go through all of threads when there are multiple replies.
-
Here's what I wrote about the laptop:
Yesterday I was on my laptop, deleting files and copying new versions of the files from a USB stick onto the laptop and all of a sudden the mouse led a life on its own and it looked like the laptop got all crazy for half a minute, changing the layout of Windows Explorer. Then it stopped. A few files were moved about. What was that?? Is that normal? I thought it was in tiptop shape? :( Shane, to inform you: me and Boggin fixed the laptop so well that the sfc scan came out 100% clean and I did Windows Repair and all.
I kinda wished you would just say this was normal.... Don't want to do anything more with the laptop either. :sad:
-
So I took a deep breath :smiley: and did the registry cleanup. 291 issues fixed. I used to use CCleaner for normal cleanups, not the registry, and I loved it for its clarity for a layperson like me, until someone told me to use Wise Disk Cleaner instead as it supposedly found more.
The sfc / scannow still came up with errors, again all these samples. Well, if we cannot get the scan right, at least I can throw away all these worthless files again. Yay! Check the screenshot I made. The language files and some samples are back but they take up >300 Mb!
Before I forget, Boggin, if I do do a re-install, will you remind me of this update that needs deleting, that Rick talks about in reply #27?
I heard IT people say that a re-installation should be done at least once every year. Do you agree?
And then, yes, my Dynamic Discs. I'm growing fond of them now, hahaha. I found another tutorial.
http://www.sevenforums.com/tutorials/26829-convert-dynamic-disk-basic-disk.html
I would use option 1 or 2. They make it seem it's no problem at all.
I still don't know the real threat the dynamic disks pose, the info I've been reading is too technical for me. PC is working fine, so Shane can take his time. I really want to stress this: if it's a lot of work, he doesn't need to bother. I'll just use the pc with my fingers crossed. Or re-install. Really. With his workload it's not worth it. Would you tell him that please, Boggin?
How about a Windows Repair All In One? Would that be useful? Or shall I just start enjoying my pc? I.e. until my next question, haha.
Oh, I already have one. :cheesy: I just learned that W7 automatically performs a defragmentation every week. I do defragmentations once in a while with O&O Defrag. Is the Windows way good enough, so I can skip a task?
-
While you say there's no rush for Shane to look at the Dynamic disks, he hasn't forgotten about you, it's just been the pressure of his computer business that has stopped him getting back to the forum.
If you ever intend to upgrade to Win 10, from that article, Win 10 won't be able to read dynamic disks so you would have to convert them, but if you are unsure how to proceed - wait until Shane gets back to you.
You don't use a defragmenter on SSDs as there's nothing mechanical on them, so turn Windows schedule off - I only defrag my HDD once a month if over 2% fragmented as over defragging can take its toll on a HDD so have never known why Windows has that default set to weekly.
However, you can get Hybrid SSDs where part of it is mechanical and Windows just defrags that bit.
Win 7 has something called TRIM to auto look after SSDs and this article will tell you how to check if it is enabled and how to enable it if not.
http://mywindowshub.com/check-enable-disable-ssd-trim-support-windows-7-windows-8-1/
I've never heard of Wise Clean, but it still puts the onus on the user as to whether to delete such files and knowing if they should be deleted.
-
Thank you, Boggin, that's very informative. I knew about the SSD, I gather from the status window of the defrag scheduler that W7 did not defrag my SSD. (I did :shocked: before I knew this, with Wise Disk Cleaner. I changed to O&O Defrag because it gives a warning when you try.) And my TRIM is enabled. Great tip!
Just read an article on a Dutch IT site stating that you should defrag daily if you use the pc intensively. See, that's why I turned to you guys. The internet states so many different views. Very confusing.
We'll wait for Shane. I know it's because of his busy schedule. I'm cool. :artist:
Do tell me if I ask too many questions. It's precisely the confusion on the net that I keep having them.
Have a nice evening! :cheesy:
-
I only get about 2% fragmentation a month and I'm on my laptop constantly.
From a recent Google about over defragging, it looks like I may have read an article that described the thrashing about when you defrag, but you would get equal thrashing when it has to look for bits in a fragmented drive.
I don't always defrag if the Analyse is small.
I've had this machine since Dec.2011 and while 5 - 6yrs is reckoned to be an average life span of a HDD, HD Sentinel gives this one a pretty decent bill of health.
BTW - Can you see the Applaud and Smite buttons in my profile as they are missing for me and I've seen the same for other users.
-
Good for you that you have such a healthy HD! 100%, wow! I'm going to do the HD Sentinel check tomorrow, see how I have been doing in two years. :)
Yes, that sounds perfectly logical to me, to only defrag when the analysis is over 2%.
I can see your applaud and smite buttons just fine. Cannot see mine, so my educated guess would be that you cannot see them because you may not give yourself karma points all the time, hahaha.
Does a smite take one karma point off??
-
I can see yours fine, but not for some other members.
I've contacted Shane about this as well as not getting email notifications, but he's that busy of late, he's probably forgotten about it :)
I suppose a Smite could take one off but it may also show it as something else - how else would anyone know that someone disapproved of a post.
-
Good point.
Let's try it out. I'll smite you now. If it takes a karma point off, I'll applaud you to give it back. :cheesy:
-
Yep, it took one off. :cheesy: See nothing else happening.
I'll give it back now. You definitely don't deserve to be smitten!
Maybe it has secretly been reported to Shane....
-
Hey, you went from 41 to 43 with my applaud!
-
Yes, it's done the same with yours - ah well....:)
I suppose now we know how to show we are really grateful :D
-
:cheesy:
-
Sorry for the late reply, I have been slammed with computer repair customers and I still have multiple to get to this week as well!
I havent done the research yet for the dynamic disks, but to be honest, if the drive is working fine I wouldnt worry about it.
Yesterday I was on my laptop, deleting files and copying new versions of the files from a USB stick onto the laptop and all of a sudden the mouse led a life on its own and it looked like the laptop got all crazy for half a minute, changing the layout of Windows Explorer. Then it stopped. A few files were moved about. What was that?? Is that normal? I thought it was in tiptop shape? :( Shane, to inform you: me and Boggin fixed the laptop so well that the sfc scan came out 100% clean and I did Windows Repair and all.
What do you mean exactly? Was the screen changing size? Or was the window you had open simply resizing?
If it was the whole screen changing size, this happens when the video driver is being updated or it crashed and restarted, the driver that is, not windows, sometimes a driver can crash without killing windows and windows will restart it. It also happens when installing a new driver and Windows is loading it.
If it wasnt the whole screen but instead the window that was open that was resizing, I have had customers who had the shift key stuck down, or some other key, and because of that it caused a lot of odd things that made them worry.
For my customer she couldnt understand why everything she clicked on selected everything, and so on. Turns out for her, her batteries in her wireless keyboard where really low and for some odd reason Windows thought the shift key was still being pressed, in fact even sticky keys popped open (Which you do when you hit shift 5 times in a row)
So you can see how something as simple as a stuck key can cause odd things, because there is a lot of combo key + mouse that Windows can do.
Shane
-
Thank you, Shane, for taking the time to write all this.
I decided to leave my dynamic discs alone. They don't seem to create any problems. The C: disk with Windows is basic, that's the important thing.
By now I know that Windows can do really odd things indeed. That issue with the laptop was the mouse doing things by itself, I had no control over it anymore. And last week I lost my dictionary files on my laptop (only the uninstall files were there???) Really strange. But then and there I decided to not put any energy and time anymore into minor things that are odd. I just re-installed my dictionaries and blessed the little Window-devils. :cheesy:
Last question: the sfc /scannow on my desktop (W7) only came up with some missing sample files like Windows videos which we couldn't repair with SFCFix.exe. As a last servicing, wouldn't it be a good idea to do a Windows Repair and then make a system image backup? I just ran CrystalDiskInfo and the external and internal harddisks are fine and the SSD is 100%. Yay!
Do you think Windows Repair would do only good? If something goes wrong, can I go back with a system restore point?
-
Boggin, can I ask the Lenovo Customer Service in Holland for a clean installation cd of W8.1? I mean, that would pose a problem with license keys, wouldn't it? I have a license key and if they send me a cd-rom then I would have two? How should I phrase such a request?
-
The disk Lenovo would send would be an OEM Recovery disk which would be a copy of the Recovery partition on your laptop.
There's a section in this article in how to create a Win 8.1 ISO disk, but where did you get the Win 8.1 key from as it was my understanding that with Win 8/8.1 that the key was built in and no longer came on a sticker key.
This article has been updated since I last read it, so read it carefully so as not to end up with a Win 10 disk.
https://www.winhelp.us/non-destructive-reinstall-of-windows-8-and-8-1.html
-
Thanks, Boggin. I read it quickly and think I can do that.
Don't have time though right now. I'll report back. :)
-
Boggin, I put Solved in the thread title. No more managing disk partitions for a while. :cheesy:
I didn't find time yet to make the W8.1 cd-rom. Would you mind if I asked you small questions here without making a new thread? I find it a bit odd to make a whole new topic about a small issue.
-
Go ahead - I'll help if I can.