Making Game: Disabling time synchronization with Hyper-V

Original Source Link

I found that when attempting to change the Date/Time settings on a Hyper-V virtualised Windows 8 OS, I found that the date would immediately change back to the correct date.

How can I prevent the Date/Time from reverting once I’ve set it?

Open the ‘Hyper-V Manager’ application on the host machine.

On the list of ‘Virtual Machines’, right-click on the VM where you want to change the Date/Time settings and click ‘Settings’.

Under the ‘Management’ section of options, select ‘Integration Services’, and uncheck the ‘Time synchronization’ option.

enter image description here

When changing the Date/Time settings from within the VM, the Date/Time will no longer revert to the Date/Time on your host machine.

It is possible to temporarily disable time synchronization for hyper-v vm’s however every hour or so the OS will sync with the hardware clock aka the bios time. As far as i known its not possible to change the bios time for hyper-v vm’s. if you disable the windows time service, the hyper-v time service and task scheduler time synchronization jobs, the OS will sync the system time to the bios clock roughly every hour.

https://answers.microsoft.com/en-us/windows/forum/all/access-bios-settings-system-date-for-vm-in-hyper-v/62f4ea6b-7bdb-433b-83d3-3fd03fd4978a

I ended up just creating a virtualbox vm and using the bios time offset command
https://winaero.com/blog/how-to-set-the-bios-date-in-virtualbox/

hopefully this feature will be implemented in the future for hyper-v.

Tagged : / /

Linux HowTo: Windows 10 Wi-Fi Networks not showing up

Original Source Link

I recently tried to get my old Gigabyte GN-WPKG PCI WLAN card to work again, as I moved my computer and was too lazy to lay new cables. Device was working perfectly, all the drivers were correct, but the Wi-Fi tab didn’t show up in Settings. After a lot of troubleshooting, I started the WLAN AutoConfig Service and it appeared.

Now, however, there are no Wi-Fi networks showing up inside the settings. Also, the Advanced Settings link is gone (that I assume should be there). Basically, I’m stuck with this:

Settings

Anyone have any ideas what to do? I already tried to delete a registry key that might have been interfering with the Wi-Fi, according to this, but the registry key isn’t found. Also tried Uninstalling device driver and restarting, but to no avail.

Open up Device Manager and find your wireless card, right click it and select update drivers. If that doesn’t work, install the latest driver’s from it’s manufacturer’s website.

Tagged : / /

Code Bug Fix: how can i set the right PATH to git bash?

Original Source Link

Okay to voice out my the problem am having. my git bash and CMD was all good. i installed MongoDB then i set a PATH for MongoDB in the environment variable (windows 10). i used C:Program FilesMongoDBServer4.2bin soon after that my git bash is no more responding to commands such as “node -version” .
how can i get to set my git and MongoDB to work perfectly

i tried env|grep PATH in my git and this is what i get.

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
ACLOCAL_PATH=/mingw64/share/aclocal:/usr/share/aclocal
MANPATH=/mingw64/local/man:/mingw64/share/man:/usr/local/man:/usr/share/man:/usr/man:/share/man
PATH=/c/Users/SAMSUNG/bin:/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/mingw64/bin:/usr/bin:/c/Users/SAMSUNG/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin:/usr/bin/vendor_perl:/usr/bin/core_perl
PKG_CONFIG_PATH=/mingw64/lib/pkgconfig:/mingw64/share/pkgconfig
INFOPATH=/usr/local/info:/usr/share/info:/usr/info:/share/info
HOMEPATH=UsersSAMSUNG
ORIGINAL_PATH=/mingw64/bin:/usr/bin:/c/Users/SAMSUNG/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin```

PATH=/c/Users/SAMSUNG/bin:/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/mingw64/bin:/usr/bin:/c/Users/SAMSUNG/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin:/c/Users/SAMSUNG/AppData/Roaming/npm:/c/Users/SAMSUNG/AppData/Local/Programs/Microsoft VS Code/bin:/usr/bin/vendor_perl:/usr/bin/core_perl

Do not see, that mongo is appears in this variable.
Try to edit your profiles and update PATH variable for git-bash
c:/users/USER/.profile
or
C:MinGWmsys1.0etcprofile

Tagged : / / / /

Making Game: How to have the UI element to automatically get the cursor focus whenever the mouse pointer is on that UI element?

Original Source Link

How to have the UI element to automatically get the cursor focus whenever the mouse pointer is on that UI element? This is so that I don’t have to click in the UI element (for example text area) so start typing. The cursor is already in there.

Tagged : /

Making Game: How can I change a Google Chrome flag with a keyboard shortcut?

Original Source Link

How can I change a Google Chrome flag (chrome://flags/) with a keyboard shortcut?

For example, I’d like to map a keyboard shortcut to set chrome://flags/ #enable-force-dark to enabled.

I use Google Chrome on Windows 7 SP1 x64 Ultimate and Microsoft Windows 10 Pro.

Tagged : / /

Making Game: Windows 10 Wi-Fi Networks not showing up

Original Source Link

I recently tried to get my old Gigabyte GN-WPKG PCI WLAN card to work again, as I moved my computer and was too lazy to lay new cables. Device was working perfectly, all the drivers were correct, but the Wi-Fi tab didn’t show up in Settings. After a lot of troubleshooting, I started the WLAN AutoConfig Service and it appeared.

Now, however, there are no Wi-Fi networks showing up inside the settings. Also, the Advanced Settings link is gone (that I assume should be there). Basically, I’m stuck with this:

Settings

Anyone have any ideas what to do? I already tried to delete a registry key that might have been interfering with the Wi-Fi, according to this, but the registry key isn’t found. Also tried Uninstalling device driver and restarting, but to no avail.

Open up Device Manager and find your wireless card, right click it and select update drivers. If that doesn’t work, install the latest driver’s from it’s manufacturer’s website.

Tagged : / /

Server Bug Fix: Windows Server 2016 0x800f081f when attempting install of Windows Backup

Original Source Link

I’m running W2K16 up-to-date as of today installed from stock Dell media. I’ve been attempting to install Windows Backup on this new server but it isn’t working. I’ve been looking in c:windowslogscbs and see that it refers to a few languages (RU/KR) that I never installed and source issues. Does anyone have any insight on how to fix this? Seems like a yet another Windows bug.

I’ve tried what is listed here. server 2016 unable to add roles or features after making server a domain controller by using lpksetup to add and then REMOVE the languages RU/KR,etc. I’m still getting the error. Oddly, in control panels when I add those languages it only offers a way to download them and not install them. I’m not sure how these languages were even included in my install as I never selected them or had a choice to do so.

What I”m seeing today in the CBS log is :

Default, start: Absent, applicable: Installed, targeted: Installed, limit: Installed, selected: Default
2020-06-09 21:20:22, Info                  CBS    Perf: Resolve chain started.
2020-06-09 21:20:22, Info                  CBS    FLOW: Entering stage: Resolving 
2020-06-09 21:20:22, Info                  CSI    [email protected]/6/10:01:20:22.493 CSI Transaction @0x2be777d5d30 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI1.30817989_1308192605:2/Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0'

2020-06-09 21:20:22, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~ko-KR~10.0.14393.0, Update: WindowsServerBackup
2020-06-09 21:20:22, Info                  CBS    Exec: Resolving component from existing package; passing NULL manifest path to PinDeployment and hoping things haven't been scavenged.
2020-06-09 21:20:22, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-BLB-Package~31bf3856ad364e35~amd64~ko-KR~10.0.14393.0, Update: WindowsServerBackup, PinDeployment: amd64_microsoft-windows-b..oyment-languagepack_31bf3856ad364e35_10.0.14393.0_ko-kr_f18c3cafe8aa2bb3
2020-06-09 21:20:22, Info                  CBS    Exec: 1 deployments need bulk staging
2020-06-09 21:20:22, Info                  CBS    Perf: Ready for complete Component closure.
2020-06-09 21:20:22, Info                  CSI    00000008 Performing 8 operations as follows:
  (0)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-BLB-Engine-SrvRes-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (1)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-SPP-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (2)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-BLB-CLI-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (3)  PrestageComponent: flags: 0 app: (null) comp: wsbcmdlet.resources, version 10.0.14393.0, arch msil, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (4)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-BLB-Engine-Proxy-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (5)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-BLB-Srv-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (6)  PrestageComponent: flags: 0 app: (null) comp: Microsoft-Windows-BLB-Engine-Main.Resources, version 10.0.14393.0, arch amd64, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
  (7)  PrestageComponent: flags: 0 app: (null) comp: blbproxy.resources, version 10.0.14393.0, arch msil, culture [l:5]'ko-KR', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-spp-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_c063cae820308d91.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-blb-cli-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_f472f60557429b21.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-b..vres-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_d39552a911e55717.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesmsil_wsbcmdlet.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_e5cf49c7cb77c3ed.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-b..roxy-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_81d11850dc73d170.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-blb-srv-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_fa74c0ebeccdf3ae.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesamd64_microsoft-windows-b..gine-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_c9b5b7c7f05c89c7.manifest
2020-06-09 21:20:22, Info                  CBS    Exec: Warning - Manifest doesn't exist for: \?C:WindowsServicingPackagesmsil_blbproxy.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_64341d7cfc36185c.manifest
2020-06-09 21:20:22, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #2666# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0xc71d57eb78->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[138]'??C:WindowsServicingPackagesamd64_microsoft-windows-spp-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_c063cae820308d91.manifest'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xc71d57ec18, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2020-06-09 21:20:22, Error                 CSI    [email protected]/6/10:01:20:22.518 (F) onecorebasewcpsilmergedntuntsystem.cpp(2898): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCBS.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200610011543.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200610002941.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200609195550.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200608205910.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200607173110.log to WER report.
2020-06-09 21:20:22, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-06-09 21:20:22, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-06-09 21:20:24, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #2665# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (OpenForBackupIntent|0x00000200), op = 'Copy', odir = NULL, oname = [l:138]'??C:WindowsServicingPackagesamd64_microsoft-windows-spp-main.resources_31bf3856ad364e35_10.0.14393.0_ko-kr_c063cae820308d91.manifest', ndir = @0x2be777c65a0, nname = [l:41 ml:63]'0299f84fc53ed6010d00000088489846_manifest', disp = Unmapped disposition: 0)
[gle=0xd0000034]
2020-06-09 21:20:24, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #2506# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 0, a = @0x2be77f87e50, mp = @0x2be77f88650, disp = 0)[gle=0x80070002]
2020-06-09 21:20:24, Info                  CBS    Failed to add one or more component [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:24, Error                 CBS    Failed to complete component closure [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:24, Info                  CBS    CommitPackagesState: Started persisting state of packages
2020-06-09 21:20:24, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2020-06-09 21:20:24, Info                  CSI    [email protected]/6/10:01:20:24.946 CSI Transaction @0x2be777d5d30 destroyed
2020-06-09 21:20:24, Info                  CBS    Perf: Resolve chain complete.
2020-06-09 21:20:24, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:24, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:24, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0, status: 0x800f081f, failure source: Resolve, start state: Installed, target state: Installed, client id: DISM Package Manager Provider
2020-06-09 21:20:24, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCBS.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200610011543.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200610002941.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200609195550.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200608205910.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Added C:WindowsLogsCBSCbsPersist_20200607173110.log to WER report.
2020-06-09 21:20:24, Info                  CBS    Not able to add %windir%winsxspending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-06-09 21:20:24, Info                  CBS    Not able to add %windir%winsxspending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2020-06-09 21:20:25, Info                  CBS    Reboot mark cleared
2020-06-09 21:20:25, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2020-06-09 21:20:25, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2020-06-09 21:20:25, Info                  CBS    FinalCommitPackagesState: Started persisting state of packages
2020-06-09 21:20:25, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
2020-06-09 21:20:25, Info                  CBS    Enabling LKG boot option
2020-06-09 21:20:25, Info                  CBS    Exec: Processing complete.  Session: 30817989_1308192605, Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.14393.0 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:28, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:28, Info                  CBS    Session: 30817989_1308192605 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2020-06-09 21:20:28, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
2020-06-09 21:20:31, Info                  CBS    Session: 30817989_1433626356 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:31, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-06-09 21:20:31, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-06-09 21:20:31, Info                  CBS    Session: 30817989_1433646367 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:31, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-06-09 21:20:31, Info                  CBS    Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-06-09 21:20:34, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{7799F1F9-2FB2-47F6-9413-690C2DB530AB}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1486572424 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    Appl: detect Parent, Package: Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~ro-RO~10.0.14393.0, Parent: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
2020-06-09 21:20:37, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed
2020-06-09 21:20:37, Info                  CBS    Appl: Evaluating package applicability for package Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~ro-RO~10.0.14393.0, applicable state: Installed
2020-06-09 21:20:37, Info                  CBS    External EvaluateApplicability, package: Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~ro-RO~10.0.14393.0, package applicable State: Installed, highest update applicable state: Installed, resulting applicable state:Installed
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{346530E9-C39D-4F6E-98C8-694B0F1BD183}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487032796 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{6C051A35-0266-4E27-8C9F-0395E311E348}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487082842 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{6FA2156B-13A0-4496-9DD2-16A1CC1C53C6}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487122879 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{DFDCDAE0-B560-493D-8788-E48255360DB3}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487152903 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{1297BE0B-CE49-47F2-97FA-07E78FDE99E4}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487192936 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{A1183A6D-22AE-48A2-B2FE-9395AE10179F}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487232968 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{C5DA0357-61F8-4639-9434-EA4422329FAC}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487272995 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{ECC70808-A351-4A33-8A23-078394424859}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487313033 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{F9D16C71-6CFD-459F-A23A-7D90FF3AED0E}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487343057 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{9D0B3520-39A5-4254-90AD-AA83CECF3DAE}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487383089 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1487483165 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{EEB5EC89-B013-4674-97CB-57C585E1B145}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1488944403 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{F9DF8BA4-A141-4A5A-B129-FD0560276743}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1488984384 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    WU creates the package, AppID:UpdateOrchestrator, UpdateID:{23C19DFC-2E24-4535-B32C-70C71BCB357D}, revision: 201
2020-06-09 21:20:37, Info                  CBS    Session: 30817989_1489024411 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-06-09 21:20:37, Info                  CBS    Appl: detect Parent, Package: Package_for_KB4561600~31bf3856ad364e35~amd64~~10.0.1.0, Parent: Microsoft-Windows-CoreCountrySpecificEdition~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present

Anyone know how I can fix this? My search so far has not yielded much more than tidbits…

Tagged :

Linux HowTo: Google Chrome will not launch (Windows 10)

Original Source Link

I have a HP ENVY running Windows 10. For some reason, the PC is unable to launch Google Chrome. When I launch the Task Manager, I see multiple Google Chrome processes running, however there is no active Google Chrome browser that I am able to see or interact with. I have tried:

  1. Restart PC
  2. Uninstall/Reinstall Chrome
  3. Disable firewall/antivirus
  4. Alt+Windows to see if it is on a different screen
  5. Other browsers work just fine.

I have also done a lot of research in other forums about why Google Chrome will not launch, and have not found a solution.

Firstly, uninstall Chrome, then create a new user with administrative rights. Install Chrome again, but this time try using http://ninite.com/ – Once installed, open, test for any website.

Logout, and back into the profile where it doesn’t work. Search for the Chrome executable and run again.

If still no joy then you will have to create a new profile for yourself and move everything (apart from the registry) over.

Your Chrome profile is usually left behind after uninstalling and reinstalling. If after reinstalling the browser you find you still have the problem, then the issue is likely with the user profile for that browser, in this case Chrome. I recommend doing the following to be sure it is fully reinstalled, with a fresh default user profile:

  1. Uninstall Chrome as before.

  2. Make sure Chrome is no longer located at
    C:Program files (x86)Google Chrome

  3. Enable hidden folders in Windows Explorer:

    https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10

  4. Open Windows Explorer (File Explorer), and go to the following folder:

    C:Users<username>AppDataLocalGoogleChrome

  5. Rename User Data to User Data.old

  6. Restart your computer

  7. Reinstall Chrome, using the offline installer (to make the install faster):

    https://www.google.com/intl/en/chrome/?standalone=1

Let us know if this works better for you. Hope everything gets working soon.

Tagged : / / /

Making Game: Google Chrome will not launch (Windows 10)

Original Source Link

I have a HP ENVY running Windows 10. For some reason, the PC is unable to launch Google Chrome. When I launch the Task Manager, I see multiple Google Chrome processes running, however there is no active Google Chrome browser that I am able to see or interact with. I have tried:

  1. Restart PC
  2. Uninstall/Reinstall Chrome
  3. Disable firewall/antivirus
  4. Alt+Windows to see if it is on a different screen
  5. Other browsers work just fine.

I have also done a lot of research in other forums about why Google Chrome will not launch, and have not found a solution.

Firstly, uninstall Chrome, then create a new user with administrative rights. Install Chrome again, but this time try using http://ninite.com/ – Once installed, open, test for any website.

Logout, and back into the profile where it doesn’t work. Search for the Chrome executable and run again.

If still no joy then you will have to create a new profile for yourself and move everything (apart from the registry) over.

Your Chrome profile is usually left behind after uninstalling and reinstalling. If after reinstalling the browser you find you still have the problem, then the issue is likely with the user profile for that browser, in this case Chrome. I recommend doing the following to be sure it is fully reinstalled, with a fresh default user profile:

  1. Uninstall Chrome as before.

  2. Make sure Chrome is no longer located at
    C:Program files (x86)Google Chrome

  3. Enable hidden folders in Windows Explorer:

    https://support.microsoft.com/en-us/help/4028316/windows-view-hidden-files-and-folders-in-windows-10

  4. Open Windows Explorer (File Explorer), and go to the following folder:

    C:Users<username>AppDataLocalGoogleChrome

  5. Rename User Data to User Data.old

  6. Restart your computer

  7. Reinstall Chrome, using the offline installer (to make the install faster):

    https://www.google.com/intl/en/chrome/?standalone=1

Let us know if this works better for you. Hope everything gets working soon.

Tagged : / / /

Server Bug Fix: Print Spooler Crashing After KB4561608 with Ricoh Printers

Original Source Link

I have a few computers that received the June update for windows 10 1809 that are now unable to print and event viewer is logging the following error:

    Log Name:      Application
Source:        Application Error
Date:          6/10/2020 10:14:13 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxx
Description:
Faulting application name: rundll32.exe_printui.dll, version: 10.0.17763.1, time stamp: 0x9816818b
Faulting module name: gdi32full.dll, version: 10.0.17763.1282, time stamp: 0xf9833b72
Exception code: 0xc000041d
Fault offset: 0x0000000000079de0
Faulting process id: 0x2134
Faulting application start time: 0x01d63f3166e8602b
Faulting application path: C:WINDOWSsystem32rundll32.exe
Faulting module path: C:WINDOWSSystem32gdi32full.dll
Report Id: 421704c0-6592-4c05-9063-e8f915744f9f
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-06-10T14:14:13.459240800Z" />
    <EventRecordID>79590</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>rundll32.exe_printui.dll</Data>
    <Data>10.0.17763.1</Data>
    <Data>9816818b</Data>
    <Data>gdi32full.dll</Data>
    <Data>10.0.17763.1282</Data>
    <Data>f9833b72</Data>
    <Data>c000041d</Data>
    <Data>0000000000079de0</Data>
    <Data>2134</Data>
    <Data>01d63f3166e8602b</Data>
    <Data>C:WINDOWSsystem32rundll32.exe</Data>
    <Data>C:WINDOWSSystem32gdi32full.dll</Data>
    <Data>421704c0-6592-4c05-9063-e8f915744f9f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

This problem seems to only affect Ricoh printers. Any idea what the fix is other than removing the update?

Some discussion elsewhere indicates this only affects PCL5 drivers, not PCL6 or PS. Can you try a different driver for the Ricoh printers?

I’m having the same issue, even with the latest PCL6 drivers for our Ricoh printer. Removing KB4560960 resolved the issue.. This is the equivalent update for build 1903.

Also KB4557957 cause the problem. Removing it resolve the problem.

Tagged : /