Recent content by JamieT

If they did a movie called "Slow & Cautious" I should star in it! 😂 .. and if they were trying to rip out all my nice safety stuff I'd tell them... "Well OK, as long as you know what you're doing?" 😂

Quite rightly said by gunrunnerjohn Use at your own risk. I did forget to say that. I feel it does the job with safety nets. But as always, have a look what the script does if you understand PowerShell. If not, it may be best not to run it.

Thanks for testing it G. I tested applying cumulative updates, there were issues to start with, with regards restoring. But I sorted that out. It's all about the version numbers. Of course, when the updates get applied the patch will get removed. It's then just a case of running it again.

No worries G, and no rush. I'd just like to know if it works for others. Yep, the Devil is in the detail! But that's where the fun/frustration lies! 😂

By the way, did you try the script? Did it do the job for you?

I've not noticed those nags. But then I am doing all my testing using 'Enterprise N'. I'll give it a look when I'm back on the clock! 😂🍻 Have a good weekend mate.

17:00 Friday, end of the working week, perfect timing! I reckon I've got it sorted after 3 days experimenting and a day making it nice for the average user! I've put it in GitHub as it feels the best place to keep/maintain it...

I'm starting to look at this again for work. I've already fixed an issue that won't be an issue for most people. Having multiple service user accounts.. Just multiple accounts that may not have logged in is an issue currently. I 'broke' my personal laptop running this script on it as is. It...

Thanks for the testing @garlin 💕 I've updated the script and will attach it here. However for me, it seems very hit and miss if it works now on my daily use PC! On my test VM it's great and works every time. Param( [Parameter(ValueFromPipelineByPropertyName)]$RemoveStartMenuItems = $True...

It feels like this is probably the best 'solution' for now. I plan to leave this now as it sorts out my particular issue for my standalone clients. But I'm keen to hear if anyone finds a way to remove this stuff in a 'fire and forget' type of way. I hope this helps pave the way for a more...

OK, so some more testing and I've made if more robust. The permissions on the appxmanifest.xml file weren't being reset correctly so I fixed that. I also tested a Windows update that installed a new version of the CBS package and it failed, so I've added another option to revert back to the...

I put the original appxmanifest.xml file back after reinstalling the tweaked appx package. So hopefully future CBS package updates will install OK. You will have to re-run the script to remove the Start menu items again. Not ideal, but we're getting there!

Oh, if you ran the first script I posted. Restore the original appxmanifest.xml file first before running this one. At: C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy appxmanifest_[earliest date/time].xml -> appxmanifest.xml

Well I just had another quick look at this and I got it to work on my laptop. I'm not sure if it was the remove package not working or how I was running it. But I put back in the ugly remove AppX package function. Anyway.. be sure to use the PowerShell that comes with Windows 11, not the one...

I'm more coming at this from just tidying up the all apps area of the start menu. The clients I'm building are quite locked down and don't have Internet access so those 3 things on the start menu just don't work.