Featured Post

1210. Presidential Debate - Trump and Harris Ridiculous

 So was there a winner of the Presidential debate or just another setup with ABC? I'll agree that Kamala was more composed and the strat...

Tuesday, August 4, 2015

705. Windows 10 Problems Part 5

UPDATE: This problem has been accepted by Microsoft and fix is due in future updates.


19. NEW PROBLEM. Note the toolbar on the E: Windows Explorer window (Left and above) (CORRUPTED) vs. a fresh Explorer window (right and below). System is trashing itself!
20. WAIT CHAIN Analysis shows DEADLOCK between 2 Explorer threads. Your multi-processing could be flawed! Too many Explore threads running at same time?
21. 10:42. I have had enough. Canceling COPY and will do ROBOCOPY. This document should have enough to confirm AND REPRODUCE several ERRORS:
a) Right-click Context Menus corrupted or just displayed wrong out of Explorer, START, TaskBar, System Tray Expansion. This problem only existed by the COPY job was running. The menus were fine after canceling the COPY task.
b) Performance problem with at last COPY
c) I would also look into Windows Defender being in the way. Should have an option on COPY to BYPASS Windows Defender when copying huge files
d) Explore toolbar gets corrupted also
e) Defender ICON does not always appear in System Tray. Also, what happened to the nice option to change what appears in System Tray (always, notification, etc.) as in W7?
f) AFTER I canceled the COPY, ALL Context menus came back correctly, but my Desktop was cluttered with ICONS that turned out be prompts for programs to use for files????? That is, if you open a file that has no file association, you get a propt to select one. However, these did NOT come up on screen until I ended the COPY job by canceling the task.
g) Lost all the Quick Access folders in Explorer that I Pinned earlier.

10 54: Restart time to see what gets cleared!

h) Displaying Properties of a large file takes a long, long time to populate SIZE. This never happened on W7.
i) COPY job showed 42,957 items to copy at start. When I started deleted E:\windows.old it counted 89,319 items for the 23.4 GB that got there! Another COPY error! The DELETE of E:\windows.old (permanently, not recycle folder) started at 11:15 and finally ended at xxxxx. Why? Just delete the index! At least the Contect Menus didn’t corrupt while it was deleting this long!
Of the above errors a-g, the following get cleared by a RESTART: a,d,f,g

The COPY job made it to 23.4GB of 35 GB before I canceled it. 2 HOURS!
------------------------------- 8/4/2015 Update -----------------

I am presently (72% complete) running TeraCopy 2.3 to do the windows.old copy to test. NO context problems running this (START, Task Bar, Explorer, System Tray all perfect and never corrupted). It has been running exactly 2 hours now, equivalent to the time when I canceled the COPY job at 23.4 GB. TeraCopy is up to 25.19 GB. So, a little faster, BUT NO PROBLEMS or CORRUPTION. I plan to run SuperCopier after this test to determine it's speed and stability on Windows 10. Will update this entry then.

Test Summary: CPU Util with TeraCopy job is between 5-12%, whereas with COPY it was 50-87%. Disk Util is hammered with TeraCopy meaning it is totally efficient compared to COPY's off and on utilization. My conclusion, since high resource use is not affecting START or Task Bar (outside Explorer) AND not affecting Explorer either, is that COPY is the culprit and it is corrupting something in cache that is common between Explorer, Task Bar, and START where Context Menus are built to display when we ask for them. The display, i.e. writing of the menu works, just the content is empty or incomplete. COPY application programmers should be hanging their heads (as the exit MSFT)! Stay tuned for more testing progress.
-------------------- 8/4/2015 Update 2 ------------------
TeraCopy finished in 3 Hr 50 Min. There were Files+Folders it couldn't copy (538 or 138019) for a total of 34.8GB or original 35.01 GB.
More importantly, the errors COPY had were NOT present with TeraCopy copy.Microsoft has a problem in COPY it needs to address.

No comments:

Post a Comment