@WrCombs said in Reboot resets Desktop Win 10 -:

So found out the user is actually corrupt, this is the 4th time this has happened according to the internal IT team, and they're looking to get the PC replaced

It’s always best to replace a corrupt user. The can leave so much of a mess.

Check out WingetUI, which can manage packages for choco, scoop, and winget.

@Pete-S using your little snippet did not clean up the pinned start menu of the initial admin user that ran it, nor the non admin user account that I subsequently created.

f2e6d053-0b72-4407-9ba8-b1d9dd3d75c8-image.png

It xbox was still in the start menu, but the rest looked gone.
da69b05a-32c4-40e7-ba6d-03ae78e2b092-image.png

@stacksofplates said in Windows 11 versus 10:

and the ever changing landscape of screen sizes.

I think we all want giant screens. That's more just a manufacturing and cost thing IMHO.

You don't need "development" for me to tell you that I want enormous screens with high resolutions, lol. I just need them to be affordable and available.

@dashrender said in Computer Name Issue: Domain Joined:

@scottalanmiller said in Computer Name Issue: Domain Joined:

@dashrender said in Computer Name Issue: Domain Joined:

@gjacobse Weird is right.

the closest I've seen is when 'nix boxes get a DHCP - they send this number that is some form of extended MAC as the hardware ID.

Interested to hear what you find out.

DHCP seems reasonable. Or there was a conflict.

in my case it's something in the way many Linux's now work. This thread talks about it.
https://community.spiceworks.com/topic/2288212-strange-extra-long-linux-mac-address-in-dhcp-active-leases

Not clicking the link, but it is the last 4 sets of the MAC address and the machine id as noted in /etc/machine-id. It is part of the DHCP RFC.

@pete-s ah ok, I don't remember it happening as much though.

@Dashrender said in Windows 10- Cant Connect to this network?:

I have seen specific devices have a hard time getting/staying connected. My old Lenovo laptop had this issue. Replacing the wireless NIC solved the problem. Others I've updated the driver and it solved, and yet others never resolved. Recommended solutions at that point were - replace the AP, replace the laptop/device.

I didn't mention updating the AP, but I suppose that should be mentioned.

Agreed, this is more likely to be hardware or driver related, than to be Windows 10 related.

@WrCombs said in Windows 10 Reboots:

So it was not a windows issue - It was the software running two or more instances of our mobile software at one time after a refresh.
What was happening was the software would restart, then try to open 2 or more at the same time causing the system to error and restart to try to clear it it's self.
Made changes to the settings in the system config files and have tested with 3 different refreshes today - It has not rebooted once.
Thanks for all the help with figuring this one out. I think i've gained a wealth of knowledge from this thread.

to expand on this - the back office becomes one of the "terminals" as an interface. When the refresh was happening the "back office terminal" was the culprit.

@wrcombs said in Uninstalling Programs (Windows 10) Using Powershell:

@jaredbusch said in Uninstalling Programs (Windows 10) Using Powershell:

@scottalanmiller said in Uninstalling Programs (Windows 10) Using Powershell:

@wrcombs said in Uninstalling Programs (Windows 10) Using Powershell:

@scottalanmiller said in Uninstalling Programs (Windows 10) Using Powershell:

Now, I thought that you had installed this via Chocolatey, not the Windows installer, though. Based on other threads.

I did install via Chocolatey does that have something to do with it?

Yes, a lot. Chocolatey is its own package management system. So Get-WmiObject knows nothing about it and can't interact with it. It's not "installed" in Windows terms, it's just "sitting there."

Actually, no. It is almost always there for windows to see. Because most chocolatey installs actually use the default windows installer. Just with a /silent switch (or whatever is appropriate).

so by this information, one of the above commands should have worked?

Not reliably. Only in the case, which might be "sometimes" and might be "often" and might be "almost always", where the one package manager used the other. So no matter how often it works, it's not "meant to work" and works only by coincidence. The coincidence might be really often, but it is still coincidence and not working by design.

@ambarishrh said in Weird blinking mouse pointer issue on my work laptop:

@dbeato said in Weird blinking mouse pointer issue on my work laptop:

@ambarishrh said in Weird blinking mouse pointer issue on my work laptop:

Explorer flickering and mouse icon flickering were unrelated as i suspected!

Final Solution that worked for me:

Mouse flickering issue fix: Uninstall Spiceworks (Suspecting it was trying to run something and may be crashing due to lack of admin rights)

For Windows explorer flickering issue, i just disabled the "preview pane" and it fixed that problem as well!

Spiceworks is not supported in Windows 10...

oh! It worked when i ran (was checking the inventory part for something i needed internally), but i guess that explains why!

Oh it will work but not supported means that you are on your own, I have been dealing with this for the last year or so on the SW community where the application has weird things happening on Windows 10 and Server 2016. As soon as the person goes back to a supported Windows 7, 8.1 or Server 2012 R2 it works fine.