Loading...

Security Update for Microsoft WIndows KB3213986

Windows 10

Hi, my computer has previously installed the old version of this update as well as the new. But every time it does, my computer has issues. The first time (back in October) my game platform, through Toshiba/Wild Tangent froze and crashed whenever I tried to play games. With this new version, it is freezing and crashing chrome browser as well as the game platform. I have to keep going into the control panel to uninstall this update. I read the description of what this update provides and from what I can tell, there is nothing on the list I need. Is there a way to keep it from being installed on my computer? I have an HP Pavilion laptop with Windows 8 that I have updated to Windows 10. Thanks, Rhonda

Answered
Network & internet 17/01/2017 0 Comments 10 views

How do I get rid of pause before logon in Windows 10?

Windows 10

Before the beautiful pictures started showing up in the background I was able to either click my mouse or pad and immediately enter my user id and password. Now it seems that I'm being forced to look at the picture for a few seconds, or fore more than a couple / three clicks, before I can enter my login information. Thanks for the pictures, but losing control of my keyboard and how fast I can things done, is not a way of ingratiating the customer base. So, how do I disable that annoying 'feature', please?

Answered
Network & internet 16/01/2017 0 Comments 2 views

Won't reboot after normal shutdown

Windows 10

Shut my computer down last night normally (though it has been symptomatic of some trouble lately - possibly RAM). This morning it won't boot up. Error message: PXE-E61: Media test failure, check cable PXE-M0F: Exiting Intel Boot Agent. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device. I have used the BIOS settings to change around my boot priority (first to Hard Disk Drive, then to Optical (I think). The closest it has come to booting up is a window allowing me to select a recovery/repair mode or start windows normally, but in both cases the screen eventually just goes black and/or goes back to the same window. Any suggestions?

Answered
Network & internet 16/01/2017 0 Comments 1 views

Had to restore laptop to factory settings and lost Windows 10

Windows 10

Hello My laptop has just restored to factory settings, the problem i have is windows 10 is no longer my operating system it is now reverted back to windows 8.1. I don't want windows 8.1 I want windows 10 on my laptop as i've been using it since the free upgrade. It would now appear to be impossible to upgrade but surely there must be a solution. On a side note all my files and pictures have all disappeared as well, there is no 'windows old' file.

Answered
Network & internet 16/01/2017 0 Comments 3 views

My CBS log.,

Windows 10

I will just post the lot, some duplicate ownership stuff in it, my PC is working atm but has problems occasionally freexes at shut down then problems rebooting requiring a restore, the last restore report problem but the PC is running OK at the momenet, outwardly at least no probs for 2 -3 days. I had to cut bits out as it was too big to post :O) Any comments? 2017-01-14 17:39:54, Info CBS TI: --- Initializing Trusted Installer --- 2017-01-14 17:39:54, Info CBS TI: Last boot time: 2017-01-14 11:10:32.484 2017-01-14 17:39:54, Info CBS Starting TrustedInstaller initialization. 2017-01-14 17:39:54, Info CBS Ending TrustedInstaller initialization. 2017-01-14 17:39:54, Info CBS Starting the TrustedInstaller main loop. 2017-01-14 17:39:54, Info CBS TrustedInstaller service starts successfully. 2017-01-14 17:39:54, Info CBS No startup processing required, TrustedInstaller service was not set as autostart 2017-01-14 17:39:54, Info CBS Startup processing thread terminated normally 2017-01-14 17:39:54, Info CBS TI: Startup Processing completes, release startup processing lock. 2017-01-14 17:39:54, Info CBS Starting TiWorker initialization. 2017-01-14 17:39:54, Info CBS Ending TiWorker initialization. 2017-01-14 17:39:54, Info CBS Starting the TiWorker main loop. 2017-01-14 17:39:54, Info CBS TiWorker starts successfully. 2017-01-14 17:39:54, Info CBS Universal Time is: 2017-01-14 17:39:54.955 2017-01-14 17:39:54, Info CBS Loaded Servicing Stack v10.0.14393.82 with Core: C:WINDOWSwinsxsamd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.82_none_5be7b69702339d1dcbscore.dll 2017-01-14 17:39:54, Info CSI 00000001@2017/1/14:17:39:54.958 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa25096c49 @0x7ffa254655bb @0x7ffa25466372 @0x7ff64b612d9d @0x7ff64b6135e0 @0x7ffa6aff7de3) 2017-01-14 17:39:54, Info CBS NonStart: Set pending store consistency check. 2017-01-14 17:39:54, Info CBS Session: 30568077_933023451 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null 2017-01-14 17:39:54, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2017-01-14 17:39:54, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2017-01-14 17:39:54, Info CBS Session: 30568077_933054501 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null 2017-01-14 17:39:54, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 2017-01-14 17:39:54, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805] 2017-01-14 17:39:56, Info CBS WU creates the package, AppID:Device Driver Retrieval Client, UpdateID:{92EC2FD0-E6D7-4983-9685-02789AFB5C86}, revision: 201 2017-01-14 17:39:56, Info CBS Read out cached applicability from TiLight for package: Microsoft-Windows-LanguageFeatures-Basic-zh-cn-Package~31bf3856ad364e35~amd64~~10.0.14393.0, ApplicableState: 0, CurrentState:0 2017-01-14 17:39:56, Info CBS WU creates the package, AppID:Device Driver Retrieval Client, UpdateID:{6B1BDF42-539B-4C6F-AD6C-727D06B404E1}, revision: 201 2017-01-14 17:39:56, Info CBS Read out cached applicability from TiLight for package: Microsoft-.0, arch Host= amd64 Guest= x86, culture [l:5]'sv-se', nonSxS, pkt {l:8 b:31bf3856ad364e35} 2017-01-14 18:13:45, Info CSI 0000476b@2017/1/14:18:13:45.605 Primitive installers committed for repair 2017-01-14 18:13:45, Info CSI 0000476c@2017/1/14:18:13:45.629 Primitive installers committed for repair 2017-01-14 18:13:45, Info CSI 0000476d Error - Overlap: Duplicate ownership for directory ??C:WINDOWSSysWOW64de-DE in component Microsoft-Windows-LSA-MSPrivs.Resources, version 10.0.14393.0, arch Host= amd64 Guest= x86, culture [l:5]'de-de', nonSxS, pkt {l:8 b:31bf3856ad364e35} repair 2017-01-14 18:18:50, Info CSI 00005a9e [SR] Verify complete 2017-01-14 18:18:50, Info CSI 00005a9f [SR] Verifying 71 components 2017-01-14 18:18:50, Info CSI 00005aa0 [SR] Beginning Verify and Repair transaction 2017-01-14 18:18:52, Info CSI 00005aa1@2017/1/14:18:18:52.731 Primitive installers committed for repair 2017-01-14 18:18:52, Info CSI 00005aa2@2017/1/14:18:18:52.754 Primitive installers committed for repair mmitted for repair 2017-01-14 18:18:54, Info CSI 00005ae7@2017/1/14:18:18:54.438 Primitive installers committed for repair 2017-01-14 18:18:54, Info CSI 00005ae8 [SR] Verify complete 2017-01-14 18:18:54, Info CSI 00005ae9 [SR] Repairing 1 components 2017-01-14 18:18:54, Info CSI 00005aea [SR] Beginning Verify and Repair transaction 2017-01-14 18:18:54, Info CSI 00005aeb Hashes for file member SystemRootWinSxSamd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' : Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=} 2017-01-14 18:18:54, Info CSI 00005aec [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2017-01-14 18:18:54, Info CSI 00005aed@2017/1/14:18:18:54.553 Primitive installers committed for repair 2017-01-14 18:18:54, Info CSI 00005aee Hashes for file member SystemRootWinSxSamd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' : Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=} 2017-01-14 18:18:54, Info CSI 00005aef [SR] Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2017-01-14 18:18:54, Info CSI 00005af0 [SR] This component was referenced by [l:161]'Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Client-Features-Package-AutoMerged-com-Deployment' 2017-01-14 18:18:54, Info CSI 00005af1 [SR] This component was referenced by [l:106]'Microsoft-Windows-ComDTC-com-Package~31bf3856ad364e35~amd64~~10.0.14393.0.f1ef22942af5b956516a3cd533741660' 2017-01-14 18:18:54, Info CSI 00005af2 [DIRSD OWNER WARNING] Directory [l:29 ml:30]'??C:WINDOWSSystem32Msdtc' is not owned but specifies SDDL in component Microsoft-Windows-COM-DTC-Runtime, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} 2017-01-14 18:18:54, Info CSI 00005af3@2017/1/14:18:18:54.678 CSIPERF - FileMapsCreated 103ms 2017-01-14 18:18:54, Info CSI 00005af4 CSIPERF - FilePI Commit 109ms 2017-01-14 18:18:54, Info CSI 00005af5@2017/1/14:18:18:54.709 Primitive installers committed for repair 2017-01-14 18:18:54, Info CSI 00005af6 [SR] Repair complete 2017-01-14 18:18:54, Info CSI 00005af7 [SR] Committing transaction 2017-01-14 18:18:54, Info CSI 00005af8 Creating NT transaction (seq 1), objectname '(null)' 2017-01-14 18:18:54, Info CSI 00005af9 Created NT transaction (seq 1) result 0x00000000, handle @0x9e4 2017-01-14 18:18:54, Info CSI 00005afa@2017/1/14:18:18:54.797 Beginning NT transaction commit... 2017-01-14 18:18:54, Info CSI 00005afb@2017/1/14:18:18:54.911 CSI perf trace: CSIPERF:TXCOMMIT;154774 2017-01-14 18:18:54, Info CSI 00005afc [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired 2017-01-14 18:21:01, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP 2017-01-14 18:21:01, Info CBS TiWorker signaled for shutdown, going to exit. 2017-01-14 18:21:01, Info CBS CbsCoreFinalize: ExecutionEngineFinalize 2017-01-14 18:21:01, Info CBS Ending the TiWorker main loop. 2017-01-14 18:21:01, Info CBS Starting TiWorker finalization. 2017-01-14 18:21:01, Info CBS CbsCoreFinalize: ManifestCacheFinalize 201 Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30568088_70078704 2017-01-14 18:57:13, Info CBS Reboot mark set 2017-01-14 18:57:13, Info CBS Winlogon: Registering for CreateSession notifications 2017-01-14 18:57:13, Info CBS Winlogon: Loading SysNotify DLL 2017-01-14 18:57:13, Info CBS Winlogon: Starting notify server 2017-01-14 18:57:13, Info CBS FLOW: Entering stage: CheckCbs 2017-01-14 18:59:25, Info CBS Repr: CBS Store check completes 2017-01-14 18:59:26, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xa577f7f820 2017-01-14 18:59:26, Info CSI 00000003 Poqexec successfully registered in [l:12 ml:13]'SetupExecute' 2017-01-14 18:59:26, Info CSI 00000004 CSI Store 2522724894448 initialized 2017-01-14 18:59:26, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:39]'10.0.14393.82 (rs1_release.160805-1735)'. 2017-01-14 18:59:26, Info CSI 00000006@2017/1/14:18:59:26.190 Starting corruption detection (InnerFlags=5) 2017-01-14 18:59:26, Info CBS FLOW: Entering stage: CheckCsi 2017-01-14 19:10:23, Info CSI 00000007 Hashes for file member SystemRootWinSxSamd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9MSDTC.LOG do not match actual file [l:9]'MSDTC.LOG' : Found: {l:32 HIZCUIacyB5KV4jprVput1klCJsx2WL4E+VaGV3fJpo=} Expected: {l:32 Q4htnI+yK+Jo0DJugTfqjq40IHkXFkIWyyAaDjFGEvo=} 2017-01-14 19:20:13, Warning CBS Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA] 2017-01-14 19:20:13, Info CSI 00000008@2017/1/14:19:20:13.966 Corruption detection complete. numCorruptions = 1, Disp = 1. 2017-01-14 19:20:14, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked. 2017-01-14 19:20:14, Info CSI 00000009@2017/1/14:19:20:14.079 CSI Transaction @0x24b60ee6fd0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30568088_70078704:1/' 2017-01-14 19:20:14, Info CSI 0000000a@2017/1/14:19:20:14.128 CSI Transaction @0x24b60ee6fd0 destroyed 2017-01-14 19:20:14, Info CBS Repr: CSI Store check completes 2017-01-14 19:20:14, Info CBS ASSERT: Assertion failed in onecorebasecbsutilincCbsArray.h(535) Index out of bound. 2017-01-14 19:20:16, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800706be]

Answered
Network & internet 16/01/2017 0 Comments 5 views

sync settings in Windows 10

Windows 10

Hi, Have a number of devices now running Windows 10. Have a problem with Sync settings between one device running Home version and other running Professional. Home version will not Sync with Professional. Is there a way to fix, or do all devices have to be Home versions to Sync?

Answered
Network & internet 16/01/2017 0 Comments 1 views

Toshiba laptop stuck on Toshiba welcome screen

Windows 10

I have a Toshiba L55 laptop with Windows 10, still under warranty. I was backing up some files to my NAS, when the copying stopped midstream, at about 55%. The laptop was frozen, so I tried control-alt-delete and I got 'preparing security options' on a blue screen (best as I can recall). This stayed up there for about 3-5 minutes. I didn't know what to do, so I shut down the computer using the power button. When I tried to reboot it, I got the black Toshiba Innovations screen and 'diagnosing your PC.' This went on for a while until 'attempting to repair your PC' came up. This was unsuccessful, so it gave me the choice of 'Advanced Options.' I tried 'Startup Repairs' and restarting to Windows 10, with no success. At this point, I don't know what to do. I would very much like to keep the data on the HD if possible as it wasn't finished backing up (new laptop, new NAS). Toshiba themselves was unhelpful, beyond telling me to send the computer in, but they won't save my data. I can also try the F12 option, which wipes the computer and reinstalls Windows from some 'secret' Toshiba partition. My more tech-savvy friend says that these are called 'dual-boot' systems and that's where some of the problem comes from, when it hands off from the Toshiba-specific stuff to booting Windows 10. My gut feeling is that my data is there, but I just need to fix how the computer gets to Windows. Searching around, I see that this 'Preparing Security Options' was a real problem on earlier versions of Windows, but don't see many references to it for Windows 10. Some earlier threads suggest something as simple as replacing the Explorer.exe file might work.

Answered
Network & internet 16/01/2017 0 Comments 1 views

Startup repair

Windows 10

Hi, i got this promblem on my lenovo g480 in which i got home basic windows 7 my system is not able to reach to windows logo. It starts with windows loading files and the i got error that windows cant repair it automatically. I dont have windows cd to repair the windows. What should i do?

Answered
Network & internet 16/01/2017 0 Comments 1 views