Separate names with a comma.
Discussion in 'HardForum Tech News' started by bigdogchris, May 21, 2019.
Retail Media Creation Utility
Academic Media Creation Utility
No worries for me, since I'm on LTSC. It will be interesting to see how this one goes, though.
I just did my work one as a test because why not, and it went fine. Settings remained the way they were no issues with domain connectivity and all my shares are still active and drive mappings are in place. No noticeable change, and it didn't take as long as I expected which meant I had to get work done that I was hoping to put off but oh well.
Just finished my 1903 update from 1809. So far so good. The right click Windows Explorer memory/cpu bug seems to be gone. Also, Firefox is no longer lagging when you close it, which was an issue I think was related to the Explorer bug on 1809.
Yeah, I just found this out as I went to upgrade a new client machine from 1803 to 1809, only to find that the Windows Update Tool only does 1903 now.
Think I'll wait, just to make sure all the kinks are ironed out first.
OK Small change I found when I did the update to one of my virtual machines (google print server) under 1809 with 1 cpu it ran perfectly fine, with 1903 it was pinned and its ram usage went from 2048 well into the 5000's, upping it to 2 CPU's has it again idling at 3-5% cpu and hanging around 1910MB of ram being used. So yeah single core systems beware.
They did change indexing around, it's possible it's just running through that. Check again tomorrow.
I also noticed that even as far back as Server 2016, it takes a while for the OS to calm down and be usable. There always seems to be a slight responsiveness issue at first.
Yeah but in the mean time people were complaining they couldn't print so I just decided to leave it at 2 CPU's but yes I can try to lower it later as a test but I have recently decommissioned 2 VM's on that machine so I have lots of cores to spare.
well the insider version failed to install on mine last night.....this likely do the same thing...but i can try unpluging all my other drives and see if that helps lol (shouldn't have to do that)
I shouldn't have to do anything inconvenient because, you know, my hardware is perfect. LOL! Dude, things happen, do you even know what it did not install? After all, the issue you are referring too would not even allow you to start the install.
will this go smooth or will they pull the update like they did the last 2 major feature updates?
Well, it appears that most of what they did on 19H1 was fixes and very few feature updates. (Heck, you know get to choose if you want to install it or not.) In fact, 19H2 is pretty much just going to be a service pack, from what I understand.
It will go smooth but, of course, if there is even the slightest issue, get ready for people to blow up the internet. I have been using the 19H1 since about the beginning of March or so in the fast ring and it went quite well.
They have pretty much put the brakes on quite a bit of the features, at least until 20H1.
So do all of these fixes make their way into 1809?
how is the new Sandbox feature?
sure, when you update to 1903...
ive been on it for weeks with insider and haven't had any issue. ymmv...
Not sure yet because I do not know how to make it work yet. I messed around for a couple of minutes a month or so ago but lost interest, at least for the being. Do you know how to make it work?
The Windows install on my moms laptop has shit the bed. I was about to do a clean install of 1809, but I guess now that this is here, I might as well use it.
I vaguely remember that Windows 10 stores its license somewhere on the hard drive. I was going to create a new partition table so the disk is blank and start from scratch. Will I have licensing issues if I do this?
not if its tied to a ms account. just install fresh and let it activate itself. if not, pull the key with magic jelly bean and enter it during install. then it will activate when install is done.
Heck, I do not even have to have a computer tied to a MS Account and Windows will activate. (It just has to be hardware that was already activated, like his mom's laptop.)
I just read about the feature but don't have any first hand use...
Settings > Apps > Apps & Features > Programs and Features > Turn Windows Features on or off, and then select Enable Windows Sandbox.
To start Windows Sandbox, open the Start menu, enter Windows Sandbox and then select it
I use local accounts only on all machines I set up. I refuse to have my local machine tied to an online account on Microsofts servers.
The laptop shipped with Windows 7 though, and was upgraded to 10 at some point, so I can probably just input the Windows 7 key from the label on the bottom (if it is still legible and not completely worn off...)
I tend to not trust black boxes. I want to understand how it reaches the conclusion that this is an activated machine. Mac address on network adapter + hardware fingerprint stored on MS Servers?
but its your moms?! yup and the installer will select the correct version to match the key.
wasn't sure on that one, so good to know.
I know it is a hardware hash but I could not tell you what combination does it. (Probably the mainboard, specifically though.) However, once it is installed cleanly, just make sure you are connected online and it should activate immediately.
Edit: I had to use my 250 GB Sata SSD to do some cloning a swapping of NVMe drives in 2 of my computers. Once I put the SSD back into my Athlon 5350 mITX system and installed 19H1, it activated without a MS account and without me needing to do anything.
All of the local users and accounts settings are gone.
Windows may just be dead to me now.
I have always been a proponent of doing all your daily tasks in a regular user account and having a separate admin account for when you need to configure stuff (even if you are the admin).
I have two local users both admin accounts right now. I need to demote one to a regular user, but I can't find the setting. Heck, I can't even find a listing of local users. It's all gone.
Unleashed TO the public? Or unleashed UPON the public?
one sounds nice, the other sounds like a biological weapon attack.
Everything's being moved to the sub par, restrictive 'settings' menu. Easier to use powershell and avoid all the wizard crap.
My understanding was that on legacy BIOS it still used the hardware hash, or link to your MS account. Newer UEFI boards the key could be stored in the motherboard BIOS (very common with OEM keys to make them non-transferable).
My experience is that results in a hellish experience if you're a "power user". Even the normal admin account is too restricted for a lot of stuff, I find.
Just installed the 1903 update on the new rig & no issues other than a service "Microsoft Push Notification" using almost 100% RAM after rebooting!!! Quickly got that under control by deleting the Notifications folder in "%LOCALAPPDATA%\Microsoft\Windows" under Safe Mode. Explorer feels a bit snappier now with Dark Mode on (seemed to lag a little when opening it under previous builds but it is now instant again). As yet to try reinstalling Adobe CS6 under it to see if that solves the issues I have been having with it closing as soon as a file is created/opened regardless of which program in the suite is used.
Eh I'll do this tomorrow on my work laptop. If its on par with all the other Feature updates, it'll hose the shit out of the laptop and I'll have to rebuild again
Not on mine, just run MMC, add it in and create you own console, quite easily, actually.
Except that those things were not moved. Seriously, have folks already forgotten how to use MMC?
In OEM computer, yes, in the bios. However, all newer motherboards are UEFI and at least on my computers, do not store the key in the bios.
Installed it this morning & reverted back to 1809 10 minutes ago as it 1903 kept launching "Windows Push Notifications Service" on every reboot which ran the memory usage up to 95% constantly for that one service!!! Even after running the "fixes" that I found online, in Safe Mode & deleting the Notifications folder at the location stated in the fixes, it still did the same after a couple of restarts. It also stopped me updating Corsair iCue software as well along with causing CCleaner to stop running after a clean started. Rollback to 1809 & all is well again.
Now to try to stop it installing itself again via Windows Update.......
Judging by the downward spiral the windows UI is in its possible m$ axes MMC in some "Feature Update" down the road, right after they change the name feature update to something else. Get used to the command line, it'll be easier when you finally switch to Linux.
Currently Known Issues with Feature Update 1903 (Dumpster Fire):
Display brightness may not respond to adjustments
Audio not working with Dolby Atmos headphones and home theater
Duplicate folders and documents showing in user profile directory
Error attempting to update with external USB device or memory card attached
Unable to discover or connect to Bluetooth devices
Night light settings do not apply in some cases
Intel Audio displays an intcdaud.sys notification
Cannot launch Camera app
Intermittent loss of Wi-Fi connectivity
AMD RAID driver incompatibility
D3D applications and games may fail to enter full-screen mode on rotated displays
Older versions of BattlEye anti-cheat software incompatible