Windows Sandbox issues

[Windows 10 User]

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

ms-resource:DisplayName

Also, Device Manager looks weird.

 

[Clanger]

When you post code the forum sometimes interprests that as a smiley, you will need to use a bbcode, see my signature link and look for

Programming code display, use the general code.​

 

[Windows 10 User]

When you post code the forum sometimes interprests that as a smiley, you will need to use a bbcode, see my signature link and look for

Programming code display, use the general code.​

Thanks, but first you said I'd need to use a bbcode and afterwards to use the general code. Anyway, I think NTLite users can see on the pictures I uploaded what I'm talking about.

 

[Clanger]

Savvy?

 

[Windows 10 User]

Savvy?

View attachment 6664

Sorry, what do you mean by that?

 

[Clanger]

Savvy? means understand.

 

[Windows 10 User]

Savvy? means understand.

No, why did you type what you did?

 

[garlin]

Vinícius Martins 1 year ago (edited) ​

For those who would like to know, I'm brazilian and I got here by searching from where the word savvy comes from. In portuguese we have the verb "sabe", which has a similar pronunciation to savvy and comes from the word "saber", which means "to know". It's common to use the verb "sabe" at the end of a phrase when we try to explain something like: "é porque eu quero passar na padaria antes de ir pra casa, sabe?" which means: "it's because I want to go to the bakery before I go home, (savvy?) do you know?" (sorry for the translation). In french there's the word "savez", and in spanish, there's "sabe". All these words have kind of the same meaning and pronunciation. Found it cool and wanted to share with you c:

 

[Windows 10 User]

It's not caused by NTLite since I installed a clean 22000.1 image and I still had these issues.

 

[garlin]

It's not caused by NTLite since I installed a clean 22000.1 image and I still had these issues.

Sandbox on clean RTM (22000.194) image. No issues.
You just proved everyone's talking point. It's not caused by NTLite, rather your decision to ignore the same basic rules of image building.

Device Manager will never be perfect, Sandbox is a virtual container (not VM) to run apps in isolation.

 

[Windows 10 User]

Sandbox on clean RTM (22000.194) image. No issues.
You just proved everyone's talking point. It's not caused by NTLite, rather your decision to ignore the same basic rules of image building.

Device Manager will never be perfect, Sandbox is a virtual container (not VM) to run apps in isolation.

I tried the latest build untouched and I still had this problem and your last paragraph just proves it's not my fault, but Windows'.

I don't know why anyone didn't tell me this (the supposed device manager problem) was normal, maybe it was just to make me waste time and/or to make me think it was my fault. What about the Settings app problem, then?

 

[garlin]

I tried the latest build untouched and I still had this problem and your last paragraph just proves it's not my fault, but Windows'.

It's not your fault for sticking to 22000.1 after everyone tells you're wrong?? WTF

We've repeated before, applying CU doesn't upgrade every file in Windows from 22000.1 to RTM, or higher. Instead of following an easy suggestion to start with RTM and check the difference, you'd rather spend all your time arguing.

Settings app's real name is Immersive Controls. Pre-release builds are buggy, that's why you stop using them when RTM ships.

 

[garson]

At the end, this is not Windows forum, but NTLite forum. There are other forums that are more into Windows.

 

[Windows 10 User]

It's not your fault for sticking to 22000.1 after everyone tells you're wrong?? WTF

We've repeated before, applying CU doesn't upgrade every file in Windows from 22000.1 to RTM, or higher. Instead of following an easy suggestion to start with RTM and check the difference, you'd rather spend all your time arguing.

Settings app's real name is Immersive Controls. Pre-release builds are buggy, that's why you stop using them when RTM ships.

Like I said, I tried the RTM and the latest builds and I still had these problems.

It's not my fault you're blind and don't read what I type.

If it's its real name, then why it only shows up as Immersive Controls now?

At the end, this is not Windows forum, but NTLite forum. There are other forums that are more into Windows.

What about Windows problems caused by a NTLite tweak (even though if it's a Window tweak) like the Paint issue? Are we supposed to not talk about them?

Regarding using the RTM build (or a newer one) instead of the .1 one, I was told in MDL that I should use the latter because the former already had a CU integrated and since I was planning to integrate the LCU, the final image would have two CUs and because of that it would be redundant and the image would bigger and so I should only apply the LCU to the .1 build. Because of that I thought integrating the LCU on a .1 build would be the same as using the latest release. If one should use a newer build than .1, why should one use the RTM build instead of the latest release, which is newer than RTM? To not waste downloading it every time a new release comes out? What's the difference between doing that and integrating the LCU on the RTM since I want to integrate the LCU every time a new CU is released?

 

[garson]

What about Windows problems caused by a NTLite tweak (even though if it's a Window tweak) like the Paint issue? Are we supposed to not talk about them?

It's not that simple. Lets say there's a reg tweak that you can manually execute, and NTLite is using same reg tweak to achieve something. If that tweak breaks something, do you still think NTLite is to blame?

Regarding using the RTM build (or a newer one) instead of the .1 one, I was told in MDL that I should use the latter because the former already had a CU integrated and since I was planning to integrate the LCU, the final image would have two CUs and because of that it would be redundant and the image would bigger and so I should only apply the LCU to the .1 build. Because of that I thought integrating the LCU on a .1 build would be the same as using the latest release. If one should use a newer build than .1, why should one use the RTM build instead of the latest release, which is newer than RTM? To not waste downloading it every time a new release comes out? What's the difference between doing that and integrating the LCU on the RTM since I want to integrate the LCU every time a new CU is released?

Well, since MDL told you to use .1 , maybe it's better place to ask?

 

[Windows 10 User]

It's not that simple. Lets say there's a reg tweak that you can manually execute, and NTLite is using same reg tweak to achieve something. If that tweak breaks something, do you still think NTLite is to blame?


Well, since MDL told you to use .1 , maybe it's better place to ask?

I didn't say NTLite was to be blamed, my point was that we can talk about it.

I already did.

EDIT: I was told it's redundant integrating the latest SSU and CU on an image since the .1 build (and not only) installs the latest ones if connected to the Internet during OOBE.

 

[francis11]

Like I said, I tried the RTM and the latest builds and I still had these problems.

It's not my fault you're blind and don't read what I type.

If it's its real name, then why it only shows up as Immersive Controls now?



What about Windows problems caused by a NTLite tweak (even though if it's a Window tweak) like the Paint issue? Are we supposed to not talk about them?

Regarding using the RTM build (or a newer one) instead of the .1 one, I was told in MDL that I should use the latter because the former already had a CU integrated and since I was planning to integrate the LCU, the final image would have two CUs and because of that it would be redundant and the image would bigger and so I should only apply the LCU to the .1 build. Because of that I thought integrating the LCU on a .1 build would be the same as using the latest release. If one should use a newer build than .1, why should one use the RTM build instead of the latest release, which is newer than RTM? To not waste downloading it every time a new release comes out? What's the difference between doing that and integrating the LCU on the RTM since I want to integrate the LCU every time a new CU is released?

Coz your starting point is 22000.1 which is full of errors as it is a beta release - for crise sake build a Windows 11 from the latest uup dump in your language - it's not that difficult and the script do it all for you - even the cleanup if you tick it before download the package to make your image will clean up the image. It will save you more time starting all over instead of posting here where no one seems to be anything than amused and having the laugh of the day.

 

[garlin]

EDIT: I was told it's redundant integrating the latest SSU and CU on an image since the .1 build (and not only) installs the latest ones if connected to the Internet during OOBE.

Maybe your sources don't understand everything.

OOBE WU performs a ZDP (Zero Day Patch) check for missing or downlevel critical updates -- which include SSU & CU. W10/W11 can do delta updates, where it only downloads UUP's missing from the local image. When you don't integrate the latest CU, WU has to download the entire package instead of the differences btw your image's CU and the current update level.

If you rather sit there, watching OOBE make the spinning circle animation...

francis11 - Minor tweak: 22000.1 which is full of errors as it is an unfinished release.

 

[Windows 10 User]

Coz your starting point is 22000.1 which is full of errors as it is a beta release - for crise sake build a Windows 11 from the latest uup dump in your language - it's not that difficult and the script do it all for you - even the cleanup if you tick it before download the package to make your image will clean up the image. It will save you more time starting all over instead of posting here where no one seems to be anything than amused and having the laugh of the day.

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?

Maybe your sources don't understand everything.

OOBE WU performs a ZDP (Zero Day Patch) check for missing or downlevel critical updates -- which include SSU & CU. W10/W11 can do delta updates, where it only downloads UUP's missing from the local image. When you don't integrate the latest CU, WU has to download the entire package instead of the differences btw your image's CU and the current update level.

If you rather sit there, watching OOBE make the spinning circle animation...

francis11 - Minor tweak: 22000.1 which is full of errors as it is an unfinished release.

I don't know. I'm very confused since they tell a different version from here.

Ok, but what about non-SSU/CU updates and IP SSU/CU updates, are they installed during the OOBE or just the public SSU/CU? If the latter, then it's better to integrate the latest updates to not lose time installing them on the OOBE or even more time doing it via WU, and if not, it would still lose a lot of time on the OOBE installing updates because of the difference between the .1 build (since I'd use it) and the latest (public, I believe), maybe the same amount of time installing the latest (public) CU via WU.

It looks like the latest builds are unfinished releases two because I have the same issues I do with the .1 build and regardless of that they're still releasing new builds so that's why they're unfinished releases.

 

[Clanger]

I'm very confused since they tell a different version from here.

Thats a very old problem many people have, 1 person says day and another person says night so wtf are you supposed to do?
nuhi has been at this game a very long time and no one here, whether you get along with them or not will guide you wrong.
Pick a single source you know you can trust and stick to it.

I have been on this new forum since day 1, literally from the day it opened and not once has anyone given me bad advice, not once.

I do visit the other place when i cannot ask something here, because it might not be appropriate for this place or because i can find something there that is not covered here.