TWINUI as Default App - Showed Up, Getting Worse

LaurieD227 said:

--I don't want to blindly run SFC /SCANNOW. There may be other things wrong in addition to the problem I observed, and I don't want to make things any worse.

I have never known SFC /ScanNow to make things worse, only better.

Your CBS log shows all system files were verified as being correct, but it found some ownership problems where folders were owned twice, such as....

Code:

2020-06-13 17:42:59, Info                  CSI    0000010d Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-13 17:42:59, Info                  CSI    0000010e Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-13 17:42:59, Info                  CSI    0000010f Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

SFC /ScanNow should fix that for you.

Bree said:

I have never known SFC /ScanNow to make things worse, only better.

Your CBS log shows all system files were verified as being correct, but it found some ownership problems where folders were owned twice, such as....

Code:

2020-06-13 17:42:59, Info                  CSI    0000010d Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-13 17:42:59, Info                  CSI    0000010e Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-13 17:42:59, Info                  CSI    0000010f Warning: Overlap: Directory \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\ is owned twice or has its security set twice
   Original owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
   New owner: Microsoft-Windows-shell32, version 10.0.18362.815, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

SFC /ScanNow should fix that for you.

Bree -

Thank you so much, that makes me feel a lot better. I'll make a point of reviewing the log file again - at first it was intimidating enough that I didn't give it a thorough review.

I have a questions about "ownership" - is it referring to ownership by an App or by a User Account?
--If the former, I may have stumbled on a cause or a contributing factor when I dug around in some of the old (2015 and 2016) TWINUI threads - one of them referenced something about Office 2010.
--I installed Office 2019 on my ProStar fairly recently, and I didn't take the precaution of uninstalling my old Office 2007. If the ownership issue is app-related, then those two may have had an argument that caused this. (As a precaution, once I found the Office reference in the thread, I went ahead and uninstalled Office 2007 this morning.)
--If it's a User Account-related thing, then advice on how to avoid it in the future would be welcome.

Regardless of the above, I'll go ahead and run SCANNOW and will report back here once I've done so.

Laurie

LaurieD227 said:

I'll make a point of reviewing the log file again - at first it was intimidating enough that I didn't give it a thorough review.

I'm not surprised you found it intimidating, there's a lot more recorded there besides the SFC results. To filter CBS.log to just see SFC's reports on corrupt (or not) files, see Option Five in the tutorial...
Run SFC Command in Windows 10
...but these ownership issues aren't actually corrupt files, so the don't appear in the filtered list. But knowing the times of the SFC reports I now knew where to look in the log for other issues it may have found.

I have a questions about "ownership" - is it referring to ownership by an App or by a User Account?

I had assumed it was referring to ownership by system accounts, but I didn't look too deeply into it....

--If the former, I may have stumbled on a cause or a contributing factor when I dug around in some of the old (2015 and 2016) TWINUI threads - one of them referenced something about Office 2010.
--I installed Office 2019 on my ProStar fairly recently, and I didn't take the precaution of uninstalling my old Office 2007. If the ownership issue is app-related, then those two may have had an argument that caused this. (As a precaution, once I found the Office reference in the thread, I went ahead and uninstalled Office 2007 this morning.)

Interesting, apps don't actually own anything, but system accounts like TrustedInstaller do own and install the apps, so you may be on to something...

LaurieD227 said:

Bad News:
--My TWINUI default app issue is unchanged, even after rebooting and going into Settings - Default Apps - Reset to Microsoft defaults.
--I also tried to change the default app for file extension ".PNG," but when I clicked on any option other than TWINUI in the drop down, I saw the "progress" indicator spin for a couple of seconds and then the window abruptly closed. The setting was unchanged when I went back in to check.
--The same thing happened when I tested it using file type "mp3."
--When I tried picking the option to look for an app in the Microsoft store, I got an error message popup. I've attached a snip of it.
So, I need to try something else, and I'm looking for advice.
--Brink's tutorial for restoring specific app defaults?
--Some sort of Windows recovery option?

There is another way to set file associations, try it on one of the 'TWINUI' problem file types, such as .png. Find a file of that type and right-click on it. Select Open with > Choose another app. It's Option Two in this tutorial.

Choose Default Apps in Windows 10


If that didn't work, you mentioned Brink's tutorial, this one?

Restore Default File Type Associations in Windows 10

I'd try it for one of the affected file associations.

If that fails too, I'd try an in-place repair install. That will reinstall Windows but keeps all your installed apps and files.

Repair Install Windows 10 with an In-place Upgrade

You probably don't want to complicate things further by upgrading to 2004 at the same time, so you should use an ISO for your current 1909. If you don't have one, use Option Six here:

Download Windows 10 ISO File

Bree said:

There is another way to set file associations, try it on one of the 'TWINUI' problem file types, such as .png. Find a file of that type and right-click on it. Select Open with > Choose another app. It's Option Two in this tutorial.

Choose Default Apps in Windows 10


If that didn't work, you mentioned Brink's tutorial, this one?

Restore Default File Type Associations in Windows 10

I'd try it for one of the affected file associations.

If that fails too, I'd try an in-place repair install. That will reinstall Windows but keeps all your installed apps and files.

Repair Install Windows 10 with an In-place Upgrade

You probably don't want to complicate things further by upgrading to 2004 at the same time, so you should use an ISO for your current 1909. If you don't have one, use Option Six here:

Download Windows 10 ISO File

Two things -

I tried the technique of selecting an image file (this time a JPG) whose default shows as TWINUI. I was able to use Open With to select an app and open the image, but if I tried to set that selected app as the Default (Open With - Choose Another App - Always Use This App) I got the same failure.

I have another option - I have a couple of recent Restore Points - June 7 and May 31. Would I be better off trying a System Restore before trying a Repair Install? Or vice versa?

I pulled a Windows 1909 ISO using Option 6, as you're right, I don't want to upgrade to 2004 right now.

LaurieD227 said:

I have another option - I have a couple of recent Restore Points - June 7 and May 31. Would I be better off trying a System Restore before trying a Repair Install? Or vice versa?

You won't have those restore points available after the repair install. It's an upgrade, even if you are 'upgrading' to the same version as you have now, and an upgrade always removes all previous restore points and clears your Update History.

Try the restore points first, and if you're lucky you won't need to do a repair install.

Bree said:

You won't have those restore points available after the repair install. It's an upgrade, even if you are 'upgrading' to the same version as you have now, and an upgrade always removes all previous restore points and clears your Update History.

Try the restore points first, and if you're lucky you won't need to do a repair install.

Thanks - didn't think about the loss of restore points.
I'm in Brink's tutorial right now to refresh myself on the steps, which brings up one more question since he describes 2 options.

Is it better to do the restore at Boot (Option 1) or from within Windows 10 (Option 2)?

LaurieD227 said:

Is it better to do the restore at Boot (Option 1) or from within Windows 10 (Option 2)?

Either should work, but a restore started from within windows can be undone, the one at boot can't. For that reason on the few occasions I've done one I always start it in Windows.