Windows 10 Installations becoming corrupted seems to have become a common problem over the last several weeks.
Windows 10
- Thread starter Glaucus
- Start date
Windows 10 Installations becoming corrupted seems to have become a common problem over the last several weeks.
They added a work around for that 2-3 builds back the shutdown menu should now have extra entries for shutdown with or without applying updates - it is still a clunky fix that doesn't solve the problems on mobile devices.
Rest goes back to what I mentioned before - MS really needs to get down to sorting the nitty gritty usability of the OS and less time on headline features.
Temporary or permanent glitching of entire OS functionality like shauncr91 posted about are not uncommon at all.
I wish they would get rid of some of the basic bugs like:-
Session "ReadyBoot" stopped due to the following error: 0xC0000188
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
The Sync Host_33bb8 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Session "ReadyBoot" stopped due to the following error: 0xC0000188
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
The Sync Host_33bb8 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.
Also can you check in your eventlog when windows defender gets update on my laptop and pc it shows in Application Log
Fault bucket 125026835750, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0
Problem signature:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.9.10586.0
P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Attached files:
C:\Windows\Temp\MPInstrumentation\client_manifest.xml
C:\Windows\Temp\WER568E.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_6c91a68d9dc3dcb8f81270a751e1bdc7adf683af_00000000_cab_074e568e
Analysis symbol:
Rechecking for solution: 0
Report ID: 6d7c3586-fdc4-11e5-85db-9c5c8ebd1b47
Report Status: 0
Hashed bucket: 4e8f2293c25f6ae615cf42d952128d60
Does anyone else get this often?
Fault bucket 125026835750, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0
Problem signature:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.9.10586.0
P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Attached files:
C:\Windows\Temp\MPInstrumentation\client_manifest.xml
C:\Windows\Temp\WER568E.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_6c91a68d9dc3dcb8f81270a751e1bdc7adf683af_00000000_cab_074e568e
Analysis symbol:
Rechecking for solution: 0
Report ID: 6d7c3586-fdc4-11e5-85db-9c5c8ebd1b47
Report Status: 0
Hashed bucket: 4e8f2293c25f6ae615cf42d952128d60
Does anyone else get this often?
The DPI thing really pees me off because it appears that Apple can handle it fine in OSX. I've just got a new work laptop and made a point of getting a FHD screen rather than the far more common now QHD, 4K or other variations of higher resolution. Watching people with high resolution laptops try and work with FHD or lower second screens, or plug into projectors is just a horror show.
There was litterally a guy who carried a magnifying glass around with him because when we he plugged it into a dock at work which had 2 FHD monitors connected his 4K, 12" laptop screen would set itself to 100% scaling and be unreadable. It was easier for him to just notnuse the laptop screen and use the magnifying glass for anything that did pop up on it rather than try and make it work properly.
I will go to great lengths to ensure that I only ever use 100% scaling as anything else is a minefield of crap.
Its not related to the latest build - happened from time to time - I filed a bug report on it nearly 2 years ago IIRC still keeps happening. Sometimes they will appear on next reboot or like half an hour later - sometimes you can pin stuff from desktop for the first 30-40 seconds after booting up but then won't work after that though might start working randomly some time later.
EDIT: OK it was 9 months ago not 2 years but still.
Last edited:
Which makes it worse, as its been an issue for multiple versions of Windows. Using a high DPI screen is painfull, using multiple screens with differing DPIs is unbearable
.Its becoming more of an issue now that more and more laptops are coming with high DPI displays.
Litterally every other mainstream OS on PC and Tablet handles DPI better than Windows.
Soldato
- Joined
- 18 Feb 2004
- Posts
- 3,095
- Location
- Lincolnshire
Respect to you, off topic i know and sorry, but never seen your sig before.
You can try System->Hardware->Device Installation Settings and disable the option there but since 1511 the behaviour has changed and it doesn't seem to reliably block the core driver installs.
You can also manage updates from the update history and tell it to remove/not install an update but if they push a new version of the update and/or on applying another major update there is a chance you'll be in the same situation again.
There is a variety of 3rd party software or taking more drastic steps to stop Windows update working as well but again they might only provide a temporary fix.
I expect at some point they'll add another clunky work around specifically for cases like this :S rather than just admit there are a diverse range of real world circumstances and just put proper manual options in there.
You can also manage updates from the update history and tell it to remove/not install an update but if they push a new version of the update and/or on applying another major update there is a chance you'll be in the same situation again.
There is a variety of 3rd party software or taking more drastic steps to stop Windows update working as well but again they might only provide a temporary fix.
I expect at some point they'll add another clunky work around specifically for cases like this :S rather than just admit there are a diverse range of real world circumstances and just put proper manual options in there.
An option to disable automatic updates won't stop Windows from downloading the wrong driver if its doing that already.
Do you know why its detecting the device wrong and downloading the wrong driver (I'm assuming its the Audio drivers)?
Do you know why its detecting the device wrong and downloading the wrong driver (I'm assuming its the Audio drivers)?
Proper manual control (as in like in 7) would let you skip it and any future updates for same driver - there is a reason such functionality exists in older/other OSes
Guys, maybe a noobish question but in regards to the windows 10 free upgrade.
I've already upgraded from Windows 7 and had one hard drive failure, and went through the process of reinstalling Windows 7 before being able to upgrade to 10 again. I've read somewhere that Windows 10 recognises your system if you make any hardware changes but if its your hard drive where the OS is installed does this still count?
I've noticed Windows 10 doesn't accept my Windows 7 key, and there is no way to exchange it etc that I know of. Can someone point me in the right direction?
I've already upgraded from Windows 7 and had one hard drive failure, and went through the process of reinstalling Windows 7 before being able to upgrade to 10 again. I've read somewhere that Windows 10 recognises your system if you make any hardware changes but if its your hard drive where the OS is installed does this still count?
I've noticed Windows 10 doesn't accept my Windows 7 key, and there is no way to exchange it etc that I know of. Can someone point me in the right direction?
HDDs are changeable, its usually motherboards were you'll need a new key (if its OEM)
Proper manual control (as in like in 7) would let you skip it and any future updates for same driver - there is a reason such functionality exists in older/other OSes
It wouldn't stop it downloading it again if there's a new or updated version of the update pushed out.
Blocking the update is just a temporary fix. Rexton should see if there's a reason why it's downloading the wrong one and investigate a solution, or let MS know so they stop pushing it out for that device.
Isnt there an option to turn off getting updates for non Microsoft products anyway, which would stop this one coming down?
Windows 7/8 (and pretty much all other OSes that have an online repository for updates) allow you full control over things like driver updates depending on settings - my 7 installs never look for or download drivers unless I manually initiate a check for updates.
Windows 10 has no such options* and it is only going to cause more problems than anything else.
Sometimes its down to specific user circumstances or 3rd party vendor tweaks, etc. there are really a diverse set of circumstances for driver incompatibilities, etc. MS would be forever chasing stuff up and implementing work arounds.
* Sure there is the device installation settings option but it doesn't really work reliably.
EDIT: On a sort of related note I guess I should look into a WSUS setup now more people have Windows 10 systems here the amount of utilisation on the main connection for Windows 10 update stuff is starting to get ridiculous even with a certain amount of local client to client sharing - though I suspect some of that is due to some systems still configured to share updates online.
Last edited: