Windows Sandbox issues

W

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:
Testing on faulty install will give errors.
And btw - old hardware is not supposed to handle w11 - if you not turn off TPM requirements.
I notized on my never ASUS laptop that Bitlocker is turned on by default after install on C drive. How will that interpret with testing on VM?
You can run powershell to circumvent the bitlock with cmd: Suspend-BitLocker -MountPoint "C:" -RebootCount 0
But i recommend to do it manually by first turn it on and next to remove bitlocker. Be sure to have a usb to save key.
And if this is to complicated - i recommend you try install a vanilla updated version of 22000.527 on your ancient hardware and see if that's possible and start from scratch there.
 
francis11 said:
Testing on faulty install will give errors.
And btw - old hardware is not supposed to handle w11 - if you not turn off TPM requirements.
I notized on my never ASUS laptop that Bitlocker is turned on by default after install on C drive. How will that interpret with testing on VM?
You can run powershell to circumvent the bitlock with cmd: Suspend-BitLocker -MountPoint "C:" -RebootCount 0
But i recommend to do it manually by first turn it on and next to remove bitlocker. Be sure to have a usb to save key.
And if this is to complicated - i recommend you try install a vanilla updated version of 22000.527 on your ancient hardware and see if that's possible and start from scratch there.
Click to expand...

Taosd said:
seems like you can't educate ignorant folks
Click to expand...

I didn't try the pt-pt/en-us .1 build, the pt-pt/en-us .1 build with the latest updates integrated, the pt-pt/en-us latest release and the pt-pt/en-us .194 with the latest updates integrated but I tried the pt-pt .194 build like Windows 10 User and I had the Windows Sandbox issues.
 
Random Guy "joined today to ntlite forums" seems to be Windows 10 User? if its true, it is really childish. I really don't think its coincidence you both used 22000.194 pt-pt and this new guy only writes to your threads. And saying i am experiencing same issue. If i'm wrong sorry but looks suspicious to me. He also knows who "nuhi" is and asking him to fix the issue in his first comment?
 
did notice, also the same 'round and round in circles alphabetti spaghetti' arguments .Just want these threads ideally shut down and ended as the issues have been noted, adised about and if left to run loose, will no doubt end up getting extremely ugly and pointless
 
Taosd said:
it is a microsoft issue, not ntlite. can we get a close on this please ?
Click to expand...

So, Windows 10 user was right.

crypticus said:
Random Guy "joined today to ntlite forums" seems to be Windows 10 User? if its true, it is really childish. I really don't think its coincidence you both used 22000.194 pt-pt and this new guy only writes to your threads. And saying i am experiencing same issue. If i'm wrong sorry but looks suspicious to me. He also knows who "nuhi" is and asking him to fix the issue in his first comment?
Click to expand...

Why do you say that? I don't think the pt-pt language isn't that unpopular and I always used the first Windows public builds, never the previous ones, so I couldn't be that user that apparently always uses or at least used the .1 build. I also didn't use the en-us builds, the .1 build with the latest updates integrated, the .194 build with the latest updates integrated and the latest release like he did.

Maybe because I had the same problems as him and like he said it weren't caused by him or NTLite but by Microsoft since they are pt-pt- specific?

What about it? Is it that strange to know the name of developer of the software I'm using? It's the first time I speak to him but I've been coming here for a few months now, although I only decided to create an account after witnessing yesterday someone also had these issues. I don't come here every day.

Clanger said:
Are we even sure its a tool issue? nuhi has said before that he spends time debugging only to find out its a windows problem.
Click to expand...

Again, apparently Windows 10 User was right.

Taosd said:
did notice, also the same 'round and round in circles alphabetti spaghetti' arguments .Just want these threads ideally shut down and ended as the issues have been noted, adised about and if left to run loose, will no doubt end up getting extremely ugly and pointless
Click to expand...

I didn't and wouldn't waste the time he apparently did by testing with many images.

Taosd said:
it isnt Clanger, it is a windows issue. IF some people used their old friend google, they would see it is a windows issue
Click to expand...

Well, you said it was caused by something Windows 10 User was doing, not that it was a Windows problem.

Also, of course I searched on Google first before typing here.

Clanger said:
Adding any fuel to a fire makes things worse. As much as it makes my pee boil dry staying silent is the better option.
Click to expand...

Then imagine being confused by another user.
 
Last edited:
Random Guy said:
Why do you say that? I don't think the pt-pt language isn't that unpopular and I always used the first Windows public builds, never the previous ones, so I couldn't be that user that apparently always uses or at least used the .1 build. I also didn't use the en-us builds, the .1 build with the latest updates integrated, the .194 build with the latest updates integrated and the latest release like he did.

Maybe because I had the same problems as him and like he said it weren't caused by him or NTLite but by Microsoft since they are pt-pt- specific?

What about it? Is it that strange to know the name of developer of the software I'm using? It's the first time I speak to him but I've been coming here for a few months now, although I only decided to create an account after witnessing yesterday someone also had these issues. I don't come here every day.



I didn't and wouldn't waste the time he apparently did by testing with many images.
Click to expand...

bruh, i think you just rumbled yourself because you know exactly what he's done without posting about it.

we had suspicions, but you have just confirmed it
 
crypticus said:
Random Guy "joined today to ntlite forums" seems to be Windows 10 User? if its true, it is really childish. I really don't think its coincidence you both used 22000.194 pt-pt and this new guy only writes to your threads. And saying i am experiencing same issue. If i'm wrong sorry but looks suspicious to me. He also knows who "nuhi" is and asking him to fix the issue in his first comment?
Click to expand...
Childish for sure - has also been there on my C64 when I was 12 years old and no internet, where I programmed 2nd degree equations in beta ;)
 
It looks like the .194 build is really the .1 with the CU which leads to it (and a SSU and another update) so there's no difference between downloading the .1 build and integrating the CU which leads to the .194 build and downloading the .194 build and integrating the updates on the former would just make the ISO bigger because it would have two kinds of CUs and SSUs, not to mention the other updates so it's better to just integrate the latest updates to the .1 build.
 
Random Guy said:
It looks like the .194 build is really the .1 with the CU which leads to it (and a SSU and another update) so there's no difference between downloading the .1 build and integrating the CU which leads to the .194 build and downloading the .194 build and integrating the updates on the former would just make the ISO bigger because it would have two kinds of CUs and SSUs, not to mention the other updates so it's better to just integrate the latest updates to the .1 build.
Click to expand...

Stop with the "Random Guy", you're fooling no one with your stealth re-edits.

Installing CU .493 on a base .1 image will generally create an ISO equivalent to .493 applied to .194. If that's true, why don't users begin with .1?
Two reasons:

1. MS doesn't test every possible update combination, they only guarantee applying CU to RTM works. If there's a patching bug, then no one can figure this one out since they're using RTM and you're the outlier on .1. Then it's your burden to convince it's not caused by .1.

2. Everyone has suggested you build an integrated image, THEN remove components. Even though NTLite tries its best, some combinations of updates and removals in the same pass can create broken builds. The processing order is critical to success, especially when it applies to features CU is updating.

The problem is you cannot predict what MS will include in the next CU. A preset which worked before can suddenly be broken by a later CU.
Separating removals in a second pass lessens that risk.

Final note: what's the size of .1 updated to .493 vs RTM updated to .493. How much disk space is saved?
Do this challenge and come back with actual results, if you want your arguments to be convincing.
 
garlin said:
Stop with the "Random Guy", you're fooling no one with your stealth re-edits.

Installing CU .493 on a base .1 image will generally create an ISO equivalent to .493 applied to .194. If that's true, why don't users begin with .1?
Two reasons:

1. MS doesn't test every possible update combination, they only guarantee applying CU to RTM works. If there's a patching bug, then no one can figure this one out since they're using RTM and you're the outlier on .1. Then it's your burden to convince it's not caused by .1.

2. Everyone has suggested you build an integrated image, THEN remove components. Even though NTLite tries its best, some combinations of updates and removals in the same pass can create broken builds. The processing order is critical to success, especially when it applies to features CU is updating.

The problem is you cannot predict what MS will include in the next CU. A preset which worked before can suddenly be broken by a later CU.
Separating removals in a second pass lessens that risk.

Final note: what's the size of .1 updated to .493 vs RTM updated to .493. How much disk space is saved?
Do this challenge and come back with actual results, if you want your arguments to be convincing.
Click to expand...

I don't care if you think I'm another user or not and what stealth edits are you talking about?

Like I convinced you as well as the other user and you states it was caused by the .1 build?

I tried that but I already have this issue after only integrating the updates.

What if an ISO becomes so big it won't fit on an USB device because the updates were applyed to an image which already had updates?

I don't care, what I care is that it's probably bigger than .1 updated to .493.

Also, how can one remove Windows Terminal from startup? It's disabled but I want to remove it and its entry doesn't even show up in CCleaner's or Revo Uninstaller's program's startup list.
 
You must log in or register to reply here.
Back
Top