Update 1709 to 1803

Thanks.Arrived where I need to be.Found lots of answers.But no time now.Will take up things tomorrow.Thanks again!!!

Hi Dalchina,

Writing you from abroad. Good morning.

If I understand the underlying meaning of your last message correctly, you recommend me to:
1. make another attempt at trying to upgrade
2. collect both setuperr and setupact logs (problem: there are several instances of varying lengths of both generated in various directories, so I'll collect all instances).
3. use the log collector - probably to avoid the snag of files too big for a normal thread to handle (I guess)

I will do all this Monday afternoon, when I'm back home.

Re your preceding message(s). I still owe you some answers, which I will send you in 2-3 hours' time.

Thanks and best regards,

H

Answers to your #47 as requested.
I'll quote the requests one by one, followed by my answers.
Please tell me when you don't understand something or when I am not clear.
YOU:
"A lot of failures listed in setupact.log appear to relate to drivers fromFile version : 2.1.51.0 built by: WinDDKDescription : Csr Bluetooth Remote Control DriverCopyright : Copyright Cambridge Silicon Radio Limited, 2010-11 Cambridge Silicon Radio LimitedProduct Version : 2.1.51.0Product Name : HarmonyCompany Name : Cambridge Silicon Radio LimitedSuggest uninstalling this if you can recognise what this belongs to."
ME:
These Bluetooth utilities have been uninstalled directly after the Microsoft Help led Upgrade attempt several days before our actual threads.They have been thoroughly eliminated via my reliable Revo Uninstaller. So, this problem should be moot. Reason for the uninstalling: suddenly messages of that utility appeared on the Windows opening screen (the one used to input the password).

YOU:
"Similarly uninstall this:Open Hardware Monitor - Core temp, fan speed and voltages in a free software gadget"
ME:
Will do - doing...

YOU:
"and MBAM"
ME:
Only trace of MBAM on my computer is an install program dating from first half of 2014!!!. Never been executed to my knowledge. Don't even know what it is!

YOU:
"SOLVED: Trouble updating to 1803 - TechTabletsCONX Failed to add driver [C:\WINDOWS\system32\DRIVERS\UMDF\uicciso.dll]seems to be a problem reported elsewhere too"
ME:
I really, REALLY don't know what you mean since this falls under your heading "uninstall". What has this "solved" to do here?! What does CONX mean? Please be slightly more explicit. In other words, what should I do? Replace that driver? Or what. This is completely esoteric.

YOU:
"Second, could you upload setuperr.log, as asked before?"
I have sent you several instances of those log files already.However, as you very well know, there are several of those logs scattered all over the place. Normal Windows "Find" does not always flag them, even if everything is of course geared to find even hidden files. So, I did a thorough search on all directories generated during the failed upgrade operations, and assembled these. Since the same names occur in different places, I have each time put them in a relevant folder.Now I hope you will find what you are looking for.This is really, REALLY everything concerning those two logs.
You will find them zipped attached.

YOU:
"I'm only guessing thisCONX ConX::Compatibility::CSystemAbstraction::GetVolumeEncryptionState: Failed to determine whether volume Q: is encrypted. HRESULT = 0x8031004a2019-02-28 21:33:51, Warning CONX Failed to determine the encryption state of volume Q:\.- might relate to your problem partition"
ME:
1. Volume Q is a volume that contains an encrypted/I guess compressed Microsoft Office trial package, that came with the installation of Windows 10. Never asked for it, never used it, never opened it, can't get rid of it. Don't want to force delete because I have noticed that touching apps or whatever that come unasked for with Windows (contravening by the way European rules, but that's another question), often has dreadful consequences.
2. I don't think it plays any part in whatever problems there are in the upgrade.
3. I have no longer a "problem partition"! Remember I sent you a report + screenshot showing that the problem HD + partition had been returned to 100% health - and that before our upgrade attempt.
So, moot.

YOU:
"But this:MIG User class hive loading error, ignoring. Hive path:C:\Users\Default\AppData\Local\Microsoft\Windows\UsrClass.dat, error: 2- may suggest registry corruption.** Please try Windows key + r, regedit- does this open normally without errors?"
My registry is perfectly in order and gets controlled regularly, apart from the automatic Windows controls.But one never knows with a complex thing like the registry, of course.
Moreover, it opens perfectly with regedit, to answer your question directly.
However, this error indicates something untoward.Is there a way to correct it?One never knows...

So this completes #47 requests. I have a good mind to throw out my computer, and start with a new one, reinstalling every program I need.

Even then I think one will never avoid Microsoft shenanigans.

By the way, knock wood, the computer keeps quiet since my little msconfig tweak.

Best,

H

The BlueTooth csr problem: I'll have Revo/cortana do a precise search on just that. Really, there should be no trace left of that BlueTooth utility which came with a BlueTooth dongle. But it seems to be something annoying somewhere indeed. And it has indeed been documented as being inimical to an upgrade. However, why would Windows want to install those drivers in the first place, let alone a service if the main program is no longer there?! Or is that an idiotic question?

Another idiotic question: can cortana find drivers, dll's etc. ?

MBAM seems to belong to Malwarebytes.What I propose to do when I retry an upgrade Monday, is to momentarily uninstall Malwarebytes...

Best,

H

Going to look immediately into this!!!
But the uicciso.dll (just looked it up) seems to provoke problems all over the place indeed!

So: even Revo, which is always so thorough, has obviously not managed to get rid of everything relating to that (Chinese) BlueTooth utility. What I am going to do Monday, is do a thorough search on the registry. Since that app has been eliminated, it won't do any harm to eliminate all references to "cambridge software", aka "csr" in the registry (don't worry, I'll back it up).

We'll get to the bottom of this. What is beyond my comprehension is that some elements like that uicciso.dll seem to play havoc with upgrades everywhere, if we are to believe Google searches. So, the Microsoft people must be aware of such recurrent problems. Why don't they do something about it?

H