Windows Sandbox issues

Windows 10 User

Active Member
After running Windows Sandbox on Windows 11, the Settings app is called "windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" if I click it on the taskbar and when I right click it's called
Code:
ms-resource:DisplayName

Also, Device Manager looks weird.
 

Attachments

  • preset.xml
    30.9 KB
  • Sem título.png
    Sem título.png
    169.1 KB
  • Sem título1.png
    Sem título1.png
    154.4 KB
  • Sem título.png
    Sem título.png
    108.5 KB
Last edited:
If you're following MDL's advice, why haven't you solved this already? This community (NTLite veterans) have repeated the same answers, and you've not seen nuhi or abbodi contradict us.

Why worry about optimization (lost time) when you have a broken build? Fix the image problems first, then you can figure out how to streamline the process later. Have you actually done a real experiment comparing your two theories? How much faster is your approach?
 
The main thing with this win10user is he is confused because he is asking same points on MDL & advised other ways.
confusion starts there & will never end. if theres a ntlite community then why asking things related to ntlite on other communities & whats the benefit user will get or achieve via doing so =======> nothing but will end up with multiple questions which will never get resolved.
 
Last edited by a moderator:
If you're following MDL's advice, why haven't you solved this already? This community (NTLite veterans) have repeated the same answers, and you've not seen nuhi or abbodi contradict us.

Why worry about optimization (lost time) when you have a broken build? Fix the image problems first, then you can figure out how to streamline the process later. Have you actually done a real experiment comparing your two theories? How much faster is your approach?

Like I said, I tried the .1 build and the latest and I had the same issues.

The main thing with this win10user is he is confused because he is asking same points on MDL & advised other ways.
confusion starts there & will never end. if theres a ntlite community then why asking things related to ntlite on other communities & whats the benefit user will get or achieve via doing so =======> nothing but with end up with multiple questions which will never get resolved.

I mainly ask things about Windows on MDL, not about NTLite.
 
i can see you are asking help regarding NTLITE on mdl & enthousiast is assisting you . what makes you not reveal the truth . why & pl dont take my questions wrong way cuz i am trying to resolve your issues
 
i can see you are asking help regarding NTLITE on mdl & enthousiast is assisting you . what makes you not reveal the truth . why & pl dont take my questions wrong way cuz i am trying to resolve your issues

Not reveal the truth? How come? I already said the users around here said a different thing than the ones on MDL.
 
here we go again.............

and i have read what has been posted on MDL .......... it is all in agreement

PEBCAK !
 
Again, I already did that and I still had these issues so that's why I think the only difference between the .1 build and the following ones is that the latter are in fact the .1 build with a SSU/CU integrated.

Meanwhile, on MDL I was confirmed this just like I was asking here and stated previously, so it's their word against yours and isn't it normal to be confused when there are two versions of the same story?
Albert Einstein said:
  • "We cannot solve our problems with the same thinking we used when we created them." ...
 
here we go again.............

and i have read what has been posted on MDL .......... it is all in agreement

PEBCAK !

That's my line.

You must be talking about yourself. Didn't you say you's ignore me? Then why sre you still replying me?

Albert Einstein said:
  • "We cannot solve our problems with the same thinking we used when we created them." ...

Then what do you want me to do when I tried the .1 build, the .1 build with the latest updates integrated, the .9 build, the .9 build with the latest updates integrated, the .194 build, the .194 build with the latest updates integrated and the latest build an in ALL OF THEM I had the same issues?
 
That's my line.

You must be talking about yourself. Didn't you say you's ignore me? Then why sre you still replying me?



Then what do you want me to do when I tried the .1 build, the .1 build with the latest updates integrated, the .9 build, the .9 build with the latest updates integrated, the .194 build, the .194 build with the latest updates integrated and the latest build an in ALL OF THEM I had the same issues?

PEBCAK

they have told you that at MDL and i am saying it again.

YOU are making more problems for yourself by being hostile towards people trying to help you. It isnt our fault that you are uneducated enough to understand what we are saying. Personally i advise on not messing around with what you do not understand and MANUALLY removing things WITHOUT ntlite. then you may find your problems may stop.
 
PEBCAK

they have told you that at MDL and i am saying it again.

YOU are making more problems for yourself by being hostile towards people trying to help you. It isnt our fault that you are uneducated enough to understand what we are saying. Personally i advise on not messing around with what you do not understand and MANUALLY removing things WITHOUT ntlite. then you may find your problems may stop.

I'm not being hostile, I'm just telling that I tried several builds and I still have the same issues. What more can I do, then?

I think I finally found what caused this fuc.... issue.

I tried the .1 en-us build and still had this issue, tried the .1 en-us build with the latest updates integrated and didn't have this issue, tried the .194 en-us build and didn't have this issue and tried the latest en-us build and didn't have this issue so it looks like it's the pt-pt language pack that messes this up, just like there's a mix of english and portuguese in the pt-pt Windows 10/11 builds. This is unnaceptable and I don't know why Microsoft didn't fix this sh... I'll have to live with these bugs since I don't want my OS in english.

Now, can anyone here or on MDL say it's still my fault or PEBCAK? How the fu.. could I know it was the pt-pt language pack messing up Windows?
 
Last edited:
I don't understand, every preset you've posted is pt-pt (19044 and 22000). There are no language packs listed. I read every preset when someone shares them. Have you been leaving out other important details??
 
That's my line.

You must be talking about yourself. Didn't you say you's ignore me? Then why sre you still replying me?



Then what do you want me to do when I tried the .1 build, the .1 build with the latest updates integrated, the .9 build, the .9 build with the latest updates integrated, the .194 build, the .194 build with the latest updates integrated and the latest build an in ALL OF THEM I had the same issues?
Coz you do your preset with tweaks and removals same time you're integrating updates (the loaded image get locked on mounted files in NTL). Just run the updates first - as they told you on MDL - and then load again and start with your customization.
Or better use latest uup witch is already ready to customize and is more quickly than NTL in updating for a finished ISO and same time cleaned up.
Begin and consider your approach to things.
To me, it sounds like you have to be pretty crazy about driving around in a carousel for way too long.
Good evening.
 
I don't understand, every preset you've posted is pt-pt (19044 and 22000). There are no language packs listed. I read every preset when someone shares them. Have you been leaving out other important details??

Maybe they're not language packs. The original image is pt-pt and I didn't add a language pack. My doubt is if the original and only language of an ISO is actually in the form a language pack but it looks like it isn't. Sorry for not explaining myself beter.

Coz you do your preset with tweaks and removals same time you're integrating updates (the loaded image get locked on mounted files in NTL). Just run the updates first - as they told you on MDL - and then load again and start with your customization.
Or better use latest uup witch is already ready to customize and is more quickly than NTL in updating for a finished ISO and same time cleaned up.
Begin and consider your approach to things.
To me, it sounds like you have to be pretty crazy about driving around in a carousel for way too long.
Good evening.

I did that, still had the same issues.

And like I told many times, I used the latest release from UUP dump a lot of times and I still had these issues.

It's definitely caused by the language of the image, just like the bad translation issue.
 
Last edited:
you don't even know your own iso's original langs.... so you probably added lang packs to your iso. or get it homebrewed from someone unexperienced. or you probably did it with a wrong way. you should use abbodi's multi language scripts to add languages. and then install cumulative/feature update over it. to make it work. adding them with ntlite is never enough. or adding a language file via dism without reapplying CU or FU never enough results in broken GUI. also i never got any problems with uup dump. i tested pt-pt and its fine on my end. the problem is as always about you and your way of doing things. like the past 50+ threads of yours over years.
 
you don't even know your own iso's original langs.... so you probably added lang packs to your iso. or go it homebrewed from someone unexperienced. or you probably did it with a wrong way. you should use abbodi's multi language scripts to add languages. and then install cumulative/feature update over it. to make it work. adding them with ntlite is never enough. or adding a language file via dism without reapplying CU or FU never enough results in broken GUI. also i never got any problems with uup dump.

I know, it's pt-pt. Did you try a non-en-us build?
 
yes i'm on tr-tr never had problems. i just expained you how and why u got that problem. i won't get it because i can properly prepare my multi language isos.

Like I said, I had bad translations problems on Windows 10 and still have them on Windows 11. I don't want a multi-language ISO, only a one-language one. I didn't integrate any language pack and I thought the original and only language of an ISO was in the form of a language pack.
 
I recommend you to use uupdump then. its impossible to get any error from it. it just downloads and runs dism commands. if your own system is not crippled and runs fine. then it can handle a cmd window.

Again, I downloaded all builds from there. I have specific pt-pt problems since Windows 10 and I also downloaded Windows 10 builds from there.
 
Back
Top