Windows 10: newmachine?

07/07/2019 00:30:56:597 -----------------------------------------------------------------
07/07/2019 00:30:56:597 NetpDoDomainJoin
07/07/2019 00:30:56:613 NetpDoDomainJoin: using new computer names
07/07/2019 00:30:56:613 NetpDoDomainJoin: NetpGetNewMachineName returned 0x0
07/07/2019 00:30:56:613 NetpMachineValidToJoin: 'WIN-A4JFEA1J135'
07/07/2019 00:30:56:629 NetpMachineValidToJoin: status: 0x0
07/07/2019 00:30:56:629 NetpJoinWorkgroup: joining computer 'WIN-A4JFEA1J135' to workgroup 'WORKGROUP'
07/07/2019 00:30:56:629 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
07/07/2019 00:30:56:660 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0
07/07/2019 00:30:56:660 NetpValidateName: name 'WORKGROUP' is valid for type 2
07/07/2019 00:30:56:722 NetpJoinWorkgroup: status: 0x0
07/07/2019 00:30:56:722 NetpDoDomainJoin: status: 0x0
Found this in the debug section of wiindows file. Anybody know what it could mean?

:)

 

Two systems, both freeze after Fall Creators update

We decided to build our own budget gaming PC that would also serve for my university work. In order to create an Windows image for the new build, I had to update our laptop to the Fall Creators update (which is a huge issue and shouldn't be a requirement
in the first place). So, boot USB made, we built the computer which worked fine. I researched the hardware carefully to avoid conflicts, and there are none. .

So, the new desktop boots up fine. Runs fine (until it freezes). There are some network issues with a WiFi dongle, but that is it. However, we get a lot of the following error in the event log:

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user [...]" I tried to fix that by following the suggested fix for that, but it didn't fix it.

The main issue is the freezes. It doesn't happen when the computer is idle, when the keyboard is being used, but specifically when the mouse is being used. We took the thing apart, double checked everything. It's not a heat
issue. Fans are working fine, we're getting great temps, even during gaming. It doesn't only happen during gaming. It can happen when working on Word (if you mouse something, OneNote (again if you use the mouse), browsing or watching a video (and say you click
on something). I reinstalled Windows and activated it with a retail key purchased from Microsoft. No fix. Drivers are updated for hardware and BIOS. It happens with Windows Defender as the anti-malware or if I install something like Bitdefender.

In the meantime, my laptop is now being used more because we don't have a reliable desktop, and it gets the same error above, AND started with the identical freezing. I managed to roll back to 1703, and so far no error message
or freezing. This has convinced me that the main issue is the Fall Creators update. Unfortunately, I can't install an older version of Windows on the newmachine rig as it's not has an earlier version. Plus, since Microsoft checked this laptop before installing
Creators Update means that it will be forced on me, and unless this bug is addressed, I won't have a functioning machine to do university work on, let alone use the machine that I just paid for the license and loads on hardware to use.

So it's not malware/viruses. Reinstalling Windows with Fall Creators update won't fix it (but downgrading it will). Messing around with uninstalling drivers that your build of Windows doesn't work with
shouldn't be something that a paying customer has to worry about with an OS. This has persisted across more than one machine and is a bug of *your* software.