How to remove Cortana (beta) app from Windows 10 May 2020 (20H1) update?

Status
Not open for further replies.

SM03

Active Member
Hello,
Is there any way to remove /disable the new 'CORTANA (BETA)' app that's present in the Windows 10 May 2020 (20H1) update ISO without disabling the 'Shell Search' functionality?

1.png

I don't use CORTANA so need to remove that, & I know that CORTANA APP is locked by the Shell Search compatibility feature, but I don't wanna disable that 'Shell Search' as that 'd disable the searching functionality in START (tried & tested)

If there is any way to remove the app without disabling the ShellSearch, suggest me that, if not, then requesting nuhi to take a look in this case & if possible do something to make this happen.
 
i alread showed it by typing it bold " not registering & not even having any default values "
Where exactly? I didn't see it anywhere where you clearly mention this, that's me who wrote that line in my earlier comment. If you wrote earlier, I might have missed, point me out there.

I will wait for completely fixed version... "mostly" will be not enough for all the work i do for AIO iso with ntlite

That's the best way to avoid (major & most of the) issues, & As I said earlier, I too will wait for the final support for 20H2 in NTL, until then, am on 20H1.
 
Why do you ask for the CBS.log when the issue doesn't have to do with yours and when I talk about a third different issue you complain? Anyway, I still have the issue I was having and I also have yours. Are you sure this issue is caused by the Cortana removal? IIRC, I also had it even when I didn't remove Cortana with NTLite.

Sometimes it looks like I have the old Settings app search problem but after closing the app and opening it again it's fine. It looks like I also have the weird icons problem showing up in Start Menu search sometimes too.

Weird, this time sfc /scannow didn't detect corrupt files and because of that (I guess) I don't have new Start Menu folders (not even after installing the latest CU [after disabling Hyper-V] sfc /scannow detected corrupt files and I had new Start Menu folders and so the removed components didn't return, I guess) and I suppose the removed components didn't return. I used the same preset except converting install.wim to install.esd to take less time when creating the image.

Now Windows doesn't install a driver related to Hyper-V after doing an install in a VM created by the latter (it also shows up in "Other devices"). The first is the Microsoft Hyper-V Virtual Machine Bus Provider driver and the latter is the Microsoft Hyper-V Virtual Machine Bus driver.

I removed all regions except mine but all off them still show up in the OOBE and removed all keyboards layouts except mine and the US one and I can still click in the ones below the portuguese keyboard layout (they're invisible) and above the US one. Am I forced to have the US keyboard layout?

Also, I can't run Office OneNote after removing Tablet PC. It states it needs Desktop Experience installed.

I asked for the log as you mentioned about the sfc /scannow & file corruption, quite relevant, isn't it? what's surprising in that?

& About the Cortana part, yes, unlike you, I know what am doing, & am 100% certain about that, my issues are fixed, not variable like yours, & neither I use different tools like you for customization. My issues don't change over the night like yours, & now that you've got the full license for NTL, I know that more issue posting will be coming here in this forum as you already started removing more & more things & tweaking in the Win ISO via full version of NTL so quite obvious is that.

Anyway, for your other different issue, like I & nuhi always told you earlier, open separate new OP, let the discussion of this thread relevant to the OP.
 
Last edited:
Where exactly? I didn't see it anywhere where you clearly mention this, that's me who wrote that line in my earlier comment. If you wrote earlier, I might have missed, point me out there.



That's the best way to avoid (major & most of the) issues, & As I said earlier, I too will wait for the final support for 20H2 in NTL, until then, am on 20H1.

idk why don't u understand what i'm writing. i specified as BOLD for u 2 times. i'm not gonna repeat myself please read again. everytime i answer u with same thing, it just extends the topic and makes it harder for nuhi
 
idk why don't u understand what i'm writing. i specified as BOLD for u 2 times. i'm not gonna repeat myself please read again. everytime i answer u with same thing, it just extends the topic and makes it harder for nuhi
Nevermind, I didn't notice earlier, so told you to point it out for me, if you don't wanna, fine by me, leave it, the main focus is to solve the issue, so just stay focused on that. I got your point anyway that you too have that same issue along with the search issue under windows settings (which I don't have) after removing the cortana.

BTW, which NTL version did you use? The latest BETA or pre-prelease version?
 
I asked for the log as you mentioned about the sfc /scannow & file corruption, quite relevant, isn't it? what's surprising in that?

& About the Cortana part, yes, unlike you, I know what am doing, & am 100% certain about that, my issues are fixed, not variable like yours, & neither I use different tools like you for customization. My issues don't change over the night like yours, & now that you've got the full license for NTL, I know that more issue posting will be coming here in this forum as you already started removing more & more things & tweaking in the Win ISO via full version of NTL so quite obvious is that.

Anyway, for your other different issue, like I & nuhi always told you earlier, open separate new OP, let the discussion of this thread relevant to the OP.

Because you complained about the fact I talked about other issues not related to these ones and about the sfc /scannow one (which is also different) you didn't and even said to post the log. Why is it relevant for you but not the other issues as well?

If so then why do you still have this issue? Also, I've been using NTLite (pre-release version) only and I still have some issues. As if it were my fault when you also have some of the problems I'm having and I've been removing with NTLite the components I was removing with MSMG ToolKit as well as the previous ones I already removed with NTLite's free version.

I already did that but why didn't you say that when I talked about the sfc /scannow problem?

idk why don't u understand what i'm writing. i specified as BOLD for u 2 times. i'm not gonna repeat myself please read again. everytime i answer u with same thing, it just extends the topic and makes it harder for nuhi

Try NTLite's pre-release version like I've told you.
 
Last edited:
issue isn't about whether the search via typing in the search bar under Windows settings is working or not, rather, it is about not registering & not even having any default values (the default option remain selected by default) in certain area under the Windows Settings after removing the Cortana part from the pre-release version of NTL.
I managed to replicate that without NTLite, as Win10 user knows over PMs since he instructed me how to use the other tool.
It must be either DISM cleanup, or latest Microsoft cumulative update bug, or some package/component which is in NTLite as well.
Will be checking today, thanks.
 
I'm not using any tool rather than ntlite and my preset was attached.
I download my iso from uupdump (that tool auto enabled netfx3.5 and cleansup updates thingy while integrating turkish language for me)

maybe that tool is the problem? but where else i'm gonna download my iso... i have to use that
 
I'm not using any tool rather than ntlite and my preset was attached.
I download my iso from uupdump (that tool auto enabled netfx3.5 and cleansup updates thingy while integrating turkish language for me)

maybe that tool is the problem? but where else i'm gonna download my iso... i have to use that
If the full patched ISO does not have that problem, then we negate the MS bug.
Just wait, it's my job to do these things.
I was busy adapting to the new Edge removal, today should finish up this and a few other things and release tonight.
 
I managed to replicate that without NTLite, as Win10 user knows over PMs since he instructed me how to use the other tool.
It must be either DISM cleanup, or latest Microsoft cumulative update bug, or some package/component which is in NTLite as well.
Will be checking today, thanks.

Like I've told you, even when using NTLite only I have that issue and for months (at least) so it's not caused by the latest CU.
 
Like I've told you, even when using NTLite only I have that issue and for months (at least) so it's not caused by the latest CU.
You never used NTLite only, read above my reply, got it with MSMG.
As said among other theries, it could be some component that is not just in NTLite, meaning it's a requirement, or piece of it - and it's not since forever as people would notice it - maybe 2004 thing.
If I need to repeat myself once more, there will be some ego releasing :)
 
You never used NTLite only, read above my reply, got it with MSMG.
As said among other theries, it could be some component that is not just in NTLite, meaning it's a requirement, or piece of it - and it's not since forever as people would notice it - maybe 2004 thing.
If I need to repeat myself once more, there will be some ego releasing :)

Yes, I did, like I've told more than once. I've had this issue after using MSMG ToolKit and NTLite and after using NTLite only. I had this problem in 1903, at least.
 
I managed to replicate that without NTLite, as Win10 user knows over PMs since he instructed me how to use the other tool.
It must be either DISM cleanup, or latest Microsoft cumulative update bug, or some package/component which is in NTLite as well.
Will be checking today, thanks.

well, nuhi you know very well that apart from (your) NTL, I don't use any (MSMG or) other tools for this image management & customization, so my outcome result (this single issue SS1 & SS2 ) is purely based on my testing via NTL. Today, am gonna test it again with a few more enhancement of mine (that we've already discussed the details in PM) & this time also I'll check & revert here if the issue persisted.

As you already confirmed that you've got the issue in MSMG, now am curious to know & see that how'd you proceed for the fix. Are you going to replicate that in NTL first before investigating & fixing, or you'll go directly for fixing?

Nevertheless, I/we will wait for the fix in next (pre-release?) build along with the official 20H2 support as well as the other 20H2 fixes.
 
Last edited:
I managed to replicate that without NTLite, as Win10 user knows over PMs since he instructed me how to use the other tool.
It must be either DISM cleanup, or latest Microsoft cumulative update bug, or some package/component which is in NTLite as well.
Will be checking today, thanks.
nuhi I just tested again & this time, with the earlier issue, START breaks completely, as if you type something (any single word i.e. A) it (START) close automatically. Sending you the preset & the video link, check PM.
 
nuhi I just tested again & this time, with the earlier issue, START breaks completely, as if you type something (any single word i.e. A) it (START) close automatically. Sending you the preset & the video link, check PM.

Sometimes a different icon still shows up after typing something in the Start Menu but after deleting what I typed and typing it again I don't have it again. Maybe this also happens with the other issues supposedly fixed by NTLite's pre-release version after removing Cortana.
 
SM03, ok, btw the Settings - Search is Cortana part, fixed in next.

Windows 10 User, ok, btw the Settings - Apps the top combo to choose where from to install the apps, is the SmartScreen feature.
If you want it functional, keep SmartScreen. Will update description.
edit: ahh it's already in, please read SmartScreen description. Will see about disabling that part of settings UI, but seems not to work unless probably Defender is kept at least. Still the dependency is now clear.

Thanks.
 
Last edited:
Windows 10 User, ok, btw the Settings - Apps the top combo to choose where from to install the apps, is the SmartScreen feature.
If you want it functional, keep SmartScreen. Will update description.
edit: ahh it's already in, please read SmartScreen description.

Thanks.

So whatever I told earlier is correct, i.e. that app installation option related issue isn't related to the Cortana part, I never had that as I kept the SmartScreen.
 
So whatever I told earlier is correct, i.e. that app installation option related issue isn't related to the Cortana part, I never had that as I kept the SmartScreen.
Who ever doubted? I misunderstood as it was a sea of reports between you two talking and I thought the issue was Settings - Search BOX not giving results, not that it cannot remember choices.
And yes, you two had different issues, not same as you also presented and confused me.
That said, it ended well, so thanks.
 
Status
Not open for further replies.
Back
Top