What the **** is TWINUI in Standard Apps and trying to change standard application closes the settings window

nuhi

NTLite developer
Staff member
Online removal never fails to piss me off.
I don't recall any reports about ongoing issues with online removal, what is yours?

TwinUI description from the tool:
Windows User Interface (TWINUI) - 32-bit
"Support for opening shortcuts, among other UI/shell communication from a 32 bit application, e.g. clicking a web link from a 32 bit app and opening it in the default web browser.

If you need it, don't remove it.

The other part of your message in the subject line, "trying to change standard application", what does that mean exactly?
A screenshot of the location where to trigger the crash might be simplest.

Thanks.
 

LIINdd

Member
The other part of your message in the subject line, "trying to change standard application", what does that mean exactly?
A screenshot of the location where to trigger the crash might be simplest.

Thanks.

I have no need for TWINUI as I know of, but it has forced itself into being every standard application in the settings. As you can see in the attached picture. When ever I try and change standard app, for example Video to VLC as soon as i click VLC the settings app is closed and the standard application isn't changed. There is no location where to trigger it, just changing any of the standard apps (that has TWINUI) will crash/close the window.

Edit: Also, if going off the preset TWINUI hasn't been removed.
 

Attachments

Last edited:

nuhi

NTLite developer
Staff member
Aha, ok, much more clear now, will test and get back to you by tomorrow (sunday now, kinda just reading reports and taking it easy).

TwinUI taking those default app places is probably OpenWith prompt, meaning same like "choose a default", but if it's not properly prompting then we have an issue.
Will know more once I try it, thanks.
 

LIINdd

Member
Aha, ok, much more clear now, will test and get back to you by tomorrow (sunday now, kinda just reading reports and taking it easy).

TwinUI taking those default app places is probably OpenWith prompt, meaning same like "choose a default", but if it's not properly prompting then we have an issue.
Will know more once I try it, thanks.

Ok, I'll just reinstall my windows now then, because I'm not sticking with this for any longer, hope you can find out what caused this, to prevent future problems with this.

My google has suggested this is something with Corrupted registry though, could be a flaw with big online removals, idk.
 

nuhi

NTLite developer
Staff member
Ok, I'll just reinstall my windows now then, because I'm not sticking with this for any longer, hope you can find out what caused this, to prevent future problems with this.

My google has suggested this is something with Corrupted registry though, could be a flaw with big online removals, idk.
You could try Host Refresh to save time reinstalling, hopefully it would not migrate the same issue.

Online removals are fine, I use them all the time for testing. It doesn't care if it's a big or small removal, this could be a newly found dependency/issue/1903 change.
If anything, online removals showed many times less issues than an offline one, reason being that image needs extra files for deploying certain features during Windows setup, while online already has that deployed so can go deeper. Those components are locked as live-only, and many are part of the OOBE compatibility.
 

LIINdd

Member
You could try Host Refresh to save time reinstalling, hopefully it would not migrate the same issue.

Online removals are fine, I use them all the time for testing. It doesn't care if it's a big or small removal, this could be a newly found dependency/issue/1903 change.
If anything, online removals showed many times less issues than an offline one, reason being that image needs extra files for deploying certain features during Windows setup, while online already has that deployed so can go deeper. Those components are locked as live-only, and many are part of the OOBE compatibility.
I tried the exact same preset but on ISO and reinstalled, problem did not appear again; how ever search is broken in both, and pressing start on both had a delay with when start menu appear. Only difference between the two was the first one I download and installed all updates BEFORE I removed components.

Third times a charm, hopefully this one is successful without issues.

EDIT: start menu still slow to open (noticeable, but not very long) and taskbar and start menu search still broken.
 
Last edited:

LIINdd

Member
The TWINUI and trying to change standard application closing the window, is 100% a problem with removing application in live mode. It’s all I did and I ended up with the same problem.
 

LIINdd

Member
Spent the better part of 10 hours trying to get a barely lite version of windows, but I get more problems than the program solves.

Can’t even get into the fucking application settings, it crashes/closes. f**k this.
 
Last edited:

nuhi

NTLite developer
Staff member
Spent the better part of 10 hours trying to get a barely lite version of windows, but I get more problems than the program solves.

Can’t even get into the fucking application settings, it crashes/closes.
On a Sunday, after being assured it will be checked on.
If there is a next time, make sure not to debug it yourself, just report the issue with a preset, and rest - potentially answering a few questions.
This type of work can be tedious, I'm at least payed for, and for some unknown reason obsessed by it.
Bugs are to be expected even with Windows development and thousands of people reviewing it, it's in the news all the time.

Anyway, it's Monday, here are my findings:

- Confirmed the default app TwinUI being shown on removed entries.
That is normal, as there is no Empty/None value for those apps. See "TwinUI" as "Windows" or "Null".
Only browser is having a "Choose a default" by default.

Crash on the other hand is not normal, also confirmed. Working on it, hopefully done by tomorrow for the planned release due to other fixes.

- Search tray issue, see here for potential info, fixed as well if it's the same situation.

- Slow start menu, is that on online or offline removal with the same preset?

- TwinUI is only 32-bit removable, that is not what's used by the 64-bit OS Settings.

Thanks, and sorry you got annoyed.
 

LIINdd

Member
On a Sunday, after being assured it will be checked on.
If there is a next time, make sure not to debug it yourself, just report the issue with a preset, and rest - potentially answering a few questions.
Well, I kind of need my operating system, to use the internet and other things, so I'm kind of forced to fix it myself in some way or another, this just happened to have bugs every single try, different ones but always consistently unusable.

Slow start menu, is that on online or offline removal with the same preset?
When ever Search Bar is broken, the Start Menu is also broken(slow to start). That's all I know about that. Apparently the settings crashing is also fixed by itself after a while, but also comes back, so it's never fixed permanently by itself. Then when I got it up and running, everything was fine I couldn't even get into the application settings, I got some error I don't remember and didn't bother writing down.

I'm using LTSC now, and while I've removed something that makes a program not start because of "Could not be read" error, I'm all good. Windows 10 is just a trash operating system, and polishing a turd and it's still a turd.

- Search tray issue, see here for potential info, fixed as well if it's the same situation.
It's not the same, he can open search. Clicking Search doesn't open the search at all, it's like its not there but it still acts like it's there by getting that "color change" when you hover above it.
 
Last edited:

Clanger

Well-Known Member
I never had the problems liting xp and windows 7 that i did have with w10 1607. I have had problems capturing and deploying LTSC when ntlite wasnt even used. If i cant capture/deploy using standard ms practices then how the hell can i expect to lite? 1607 left such a bad taste i am only tweaking ltsc, so far so good but it aint as lite as i want it tobe. Blame ms for ignoring bugs and focusing on silly new features and this twice yearly major update malarky that serves no real purpose other than satisfying social media and bling junkies. Luckily time honoured tweaks are giving me good results, but its not lite :( Even msmg has bugs and if people combine both tools then they are walking into a minefield.
 

nuhi

NTLite developer
Staff member
LIINdd, fixed and released build 6975, thanks for reporting.
Let me know if you have any remaining issues, remember not to waste time debugging it.
 

LIINdd

Member
nuhi

Instead of opening a new thread, I figured I'd tell you about something;

When doing a live removal of applications, they tend to stick around in the start menu, reboot doesn't fix it. It also leaves ghost buttons in Taskbar for removed applications (Edge/Store is the two that are Pinned to Taskbar at the start). This doesn't effect Offline removals, since they are not cached.

A fix for the start menu things are, I'm not sure how you'd incorporate this into the program is to go to "%LocalAppdata%\Packages" and locate Microsoft.Windows.ShellExperienceHost_XXXX or Microsoft.Windows.StartMenuExperienceHost_XXXX, and go into the folder TempState and delete the content, then just restart the "StartMenuExperienceHost.exe" or "ShellExperienceHost.exe" process. I'm just guessing, but I think the difference in what the process is called and the place the files you need to delete is located depends on the Windows version, as that's the difference between my Daily Driver and my VM. You'd have to test it for yourself.

Well this was messy, I hope you understand it though. It's not game breaking, but might be annoying to fix for people, as they can't just reboot to fix this (at least hasn't worked for me).
 

nuhi

NTLite developer
Staff member
A fix for the start menu things are, I'm not sure how you'd incorporate this into the program is to go to "%LocalAppdata%\Packages" and locate Microsoft.Windows.ShellExperienceHost_XXXX or Microsoft.Windows.StartMenuExperienceHost_XXXX, and go into the folder TempState and delete the content, then just restart the "StartMenuExperienceHost.exe" or "ShellExperienceHost.exe" process. I'm just guessing, but I think the difference in what the process is called and the place the files you need to delete is located depends on the Windows version, as that's the difference between my Daily Driver and my VM. You'd have to test it for yourself.
Thanks for the tip, will review and implement.
 
Top