More likely they have used it for a while but someone else has also started using it or have discovered the exploit and were about to release it, so they decided to call it first in an effort to create “goodwill” towards the honourable spying on everyone agency that is the NSA.
Or some idiot analyst at the NSA decided to take the attack tools with him home and gave Kaspersky Cloud Analytics another dump of malware because he was too stupid to disable the ‘Upload unknown files to the internet then blame the russians for hacking us, using it as a pretext to block kaspersky av to be used in government agencies…’
stusser
4398
Well yes, that’s what I implied by “as far as we know”.
So this was my Wednesday…
So, disregarding how idiotic the .NET installers are (not installing in any way like anything else from MS) the latest update to .NET framework - upon failure during installation, seems to have done the following.
(The reason it fails is that I have my %TEMP% folders set to a ramdrive. Everything else BUT .NET updates will work with this, but .NET Updates do something weird… When the %TEMP% folders are set to a normal folder, say C:\TEMP, the .NET installer will look for the disk with the biggest free size, and instead of using %TEMP% like everything else, will pick that disk and put it in the root folder with a cryptic foldername, like w:\7b77fff65737d83c41674cf3)
Anyway, what the shitty update from Microsoft did was:
- Not set a restore point
- Removed all traces of .NET from registry
- Removed .NET 4.8 from the control panel / add remove windows features
- Removed mscoree*.dll files from system32/syswow64
- Probably a bunch of other malfeasance
- Edited: Yes, most of the files under c:\windows[Microsoft.NET](https://microsoft.net/) are gone.
To fix this, there is a bunch of tools available
- The .net repair tool from MS does nothing
- SFC does nothing
- Trying to manually install 4.8 from ndp48-devpack-enu, ndp48-x86-x64-allos-enu, ndp48-web does nothing, because they are blocked by a idiotic check that says “They are already installed” (probably a OS check, will try to look into this more).
- Trying to repair using the above installer packs does nothing.
In addition
- trying to launch powershell, which relies on .NET does not work.
- Trying to run the wushowhide.diagcab does not work because .NET isn’t working (I had previously hid some updates, was going to look for them
- Trying to removing updates from the “Windows 10 Update” list only shows me the old control panel (which would’ve been good, except no .NET updates are listed there).
So guess like I have to manually recreate all the missing .NET information using procMon and another Windows 10 computer as ‘template’.
What the f.
Or is there some other .NET repair tool that I do not know about?
Seems like I am not alone - also on 1903:
https://answers.microsoft.com/en-us/windows/forum/all/net-framework-issues/39432447-e1e0-456a-9ca8-42fddac242c5
Update:
Got Powershell working again.
- Copied the full c:\windows[microsoft.net](https://microsoft.net/) folder from another 1903 installation
- copied all .NET registry keys under hklm\software and hklm\software\wow64node…
- Launched powershell with procmon which found out these files were missing
- UCRTBASE_CLR0400.dll
- VCRUNTIME140_CLR0400.dll
- Copied those files back into system32/syswow64 from their c:\windows\winsxs folders.
EventVwr also working now, no longer crashing with MMC error.
MicrosoftProgram_Install_and_Uninstall.meta - also working.
RzSynapse (.net app) still not working.
- C:\Windows[Microsoft.NET](https://microsoft.net/)\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll —> System.ComponentModel.Win32Exception: The specified module could not be found
- Which is funny, since the file is there
- Procmon says this file is missing MSVCP140_CLR0400.
- Copied this file back and Razer Synapse is working.
Seems like all the _CLR0400 files were removed as well as .NET Framework.
Windows Store and most of those apps (… that I do not use, except for Kali Linux) not working.
Seems harder to fix than ‘normal’ windows things, which is impressive by MS.
The Windows update to IIS broke Deltek’s server, so our company cannot enter timesheets as of right now. Pretty smooth!
fdsaion
4403
jfc that sounds like a wipe and reinstall situation.
The last time MS broke Store on my home PC, it took what felt like endless hours of research and failed techniques to get it back (there’s no one-size-fits-all). In the end, reinstalling would have actually saved me time and frustration.
Figured I’d try using the update assistant to install 1909…
The fucking tool starts scanning every executable on every hard drive before it does the installation… triggering my antivirus into overdrive because I have a lot of “stuff” collected over the years.
Whatever happend to it just checking whatever is installed and pertinent to Windows instead of jumping to a drive with nothing windows related on it…
Fuck you microsoft.
Any tips on what you did, besides installing Win10 all over again.
Win10 is worst OS MS ever put out, shame it is the only one supporting G-sync on Freesync monitors and has HDR (shitty) support.
Had trouble adding a domain account during OS install phase (my first time). It took several attempts to get it right since I clicked too fast. There is no ‘Back’ button in install/setup. Meh.
I tried to go through a bunch of Poweshell commands from the Internet, which I later learned were slightly off and needed tweaking thanks to the instructions I found being out of date. The long and short of it was getting all the instructions first, then disabling my 3rd party AV (Avast), then eventually I found some steps here which eventually got me on my way (step 4 was the one which finally did it for me; the referenced download is from MS, otherwise I wouldn’t have risked it, btw).
rei
4408
I don’t know why some people who are like my friend who never updated their Win10 Surface Pro since getting it 2 years ago until yesterday after the certificate dll news hit the mainstream. Then complained about how long it took and THIS was the reason she never wanted to update.
Nesrie
4409
I had a friend who was on cell internet, and she told me every time, every single time she started her computer it would be fine at start and then too slow to really use internet. It turned out it was her updates. She had it set to auto download but she never let it finish because her being online is like 2 minutes on e-mail and then a minute online so probably not long enough to actually let everything download on such a slow speed to begin with. She would just close the lid.
So I sat there and let it download everything, restarted it a few times to do the updates and then i told her just leave it open for like an hour or so once in awhile so all the downloads complete and install. My mom was the same way, didn’t understand these things were happening in the background and needed to finish.
The people I know who actually use computers, privately, just leave them up so often and on that downloads happen behind the scene or we go get them.
Mine started doing something after I closed the lid one night. Not sure what. (First time laptop owner.)
Nesrie
4411
That new computer you just got is your first laptop? Well hey, it’s probably not as bad as you think it is. Modern laptops are pretty good these days and portability is so handy. It saved me a lot of traveling to tell people to just bring the thing over rather than me going to some desktop shoved in a corner somewhere with spiders living in it.
Yeah, not sure the 2-in-1 screen was the right choice. I could have gotten a business laptop with better specs for the same price.
MS can’t win. They force restarts, and social media gets flooded with people complaining about critical work being lost. They don’t force restarts, and a not insignificant portion of the population is probably like your friend who just close the lid and never, ever, ever restart their computers.
Nesrie
4414
Well they could at least stop breaking stuff with their fixes. I mean the forcing wouldn’t be so bad if you didn’t wind up with your system screwed and a shrug from Microsoft.
Personally I usually waited a few months to take new updates just to get that sort of stuff out of the way. When they forced me to update… couldn’t do that anymore.
Found a way to force .NET 4.8 to reinstall.
Windows store is still broken, but fuck that shit - at least until the DCH Drivers are the only ones on offer… (which they probably will, knowing the way MS are going… )
