Sorry for the delay in replying.
First a quick update for
Boggin, or anyone else.
I closed the 'stuck' Tweaking Repair task by clicking on the 'X' with the Red Background, expecting it to stop the 'All Repairs' task I had started running, as Administrator, in Safe Mode, with Network. Instead it stopped the current stuck individual task and jumped to the next one of the 49 tasks in the 'All Repairs' list. As it did so I briefly saw a flash of a log repeating something like '... can't access or access denied ... file in use ...' then the log was gone!! I got the meaning of it though and assume it indicated it had spent all those 25 hours I'd left it running repeatedly trying to access a file that another process was using, (not that this was indicated on the screen). It progressed on to all the other tasks in the list and completed them, though there was one task on which it appeared to get stuck, but as I was was clicking between the log and task list, and was about give up on that task and click 'X' to cancel it, the task finished. (I
don't think I did click 'X', so
I think it completed ok!.) Anyway the 'All Repairs' task moved on down the list and finished.
So I believe all repairs were completed except one, (maybe two).
But having had at least one task fail I decided to rerun the full repair list again, in Safe Mode, but this time without Network, in case it was a Network related process that was using the file causing it to get stuck. I also thought I'd run the tasks one at a time so I could track where any problems were occurring more easily. So that's what I'm currently doing. On task '04 - Register System Files', which is where I think it got stuck before, its trying to register C:\windows\sysWOW64\FPWPP.DLL but is again stuck. If this is because it's in use by another process, I've no idea which one, or what I could do to get the registration to proceed. Neither can I see a way to skip to the next item in that 'Register System Files' repair script. Also, I guess if I stop the task, it will mean that the registration repair of all the subsequent System Files won't be done. That may, or may not, be a problem!
Also as clarification for
Boggin , I'm not trying to sort out my MS Surface, running fine which is why I'm using it to submit these posts.
Its my other machine that's having problems. It's a
HP Pavilion dv6 which, to answer
Boggin's question in his last post, does have Radeon Dual Graphics and Quad Core. The processor is AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597 Mhz, 4 Core(s), 4 Logical Processor(s). I've been trying do a repair this PC since early September following repeated BSOD with 'Stop code: DPC WATCHDOG VIOLATION'. The advice for fixing this amounted to a rather vague, "update the drivers and run Windows Update", ... which didn't fix it. So after many attempts at different resolutions I decided to do a Windows 10 re-installation, using the Microsoft MediaCreationTool as I understand this will mean I can avoid having to reinstall all my Apps. However every time I ran it, it fails, after "Creating Media", it 'cleans up and closes', and doesn't progress to the installation stage! This is the reason why I followed Bitec69's YouTube advice and decided to run the Tweaking Repairs as I hope, if I can run all the repairs, that the MediaCreationTool may then succeed.
I'm not sure if the following have any relevance to resolving these problems but I'll restate them now in case they do. The computer originally had AMD Catalyst Suit installed and AMD had repeatedly, over the previous couple of years, sent updates for this, which, when run responded with "this update can't be applied to the chip-set and version of AMD Catalyst Suit installed", (why offer me the update then ...) I did try to update the drivers in the normal way as
Boggin describe, and it responded that the current driver was the best available, but I thought I'd checkout AMD's site to be sure. On their site they advised against using AMD Catalyst Suit on Windows 10 and said that using the Windows 10 generic divers was the best option. So I uninstalled the originally installed AMD Catalyst Suit thinking the Windows 10 generic offer would be up to date and better, it worked ... or did it? The properties for all of drivers reported that they are working properly, but this isn't consistent with Device Manager which now displays the warning triangles mentioned in my previous post. (November 08, 2018, 09:37:28) Why is that?
Four groups of drivers show a triangular warning symbol even though each driver said it was working fine. They were;
-Display adaptors - AMD Radeon HD 6520G and HD 7400M Series
-IDE ATA/ATAPI controllers - AMD SATA Controller, ATA Channel 0 & 1, and Standard Dual Channel PCI IDE Controller
-Sound, video and game controller - AMD High Definition Audio Device
-Storage controller - Microsoft Storage Spaces Controller
Also Boggin can you, or anyone else, tell me the meaning of these items listed in the C:\$Windows.~BT\Panther\setuperr.log which is created when I try running Windows MediaCreationTool1803.exe that i mention two posts ago. (November 08, 2018, 06:40:07)
Here's the setuperr.log contents:
2018-03-04 05:29:11, Error MOUPG CInstallUI::GetDefaultLanguage(1785): Result = 0x80070002[gle=0x00000002]
2018-03-04 05:41:30, Error MOUPG CSetupManager::GetDUSetupResults(5499): Result = 0x80070490
2018-03-04 05:41:38, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104
2018-03-04 05:41:38, Error MOUPG CDlpTask::Cancel(979): Result = 0xC1800104
