News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Daily Archives: August 16, 2018

  • Minimum Versioning Coming Soon to SharePoint Online & OneDrive for Business Libraries

    Posted on August 16th, 2018 at 23:21 Kirsty Comment on the AskWoody Lounge

    Modified in Office 365 Roadmap on August 14, 2018:

    Versioning settings in OneDrive for Business, Groups and team sites in SharePoint Online
    All SharePoint and OneDrive libraries will be set to retain a minimum of one hundred major versions. Existing libraries that have versioning enabled but are set to retain fewer than one hundred major versions will be updated to retain the new minimum. Libraries already set to retain one hundred or more major versions will not be affected, including those with the default setting of five hundred. With these changes, the Document Library Settings page will no longer support the ability to disable versioning or configure it to retain fewer than one hundred versions.

    Again, there are reports of customers pushing back on Microsoft’s changes, and Microsoft have advised that organisations will be able to avoid this change on “Office 365 Tenants”, if they act before September 30th – “Otherwise, we will roll out the versioning setting update to your tenant in October 2018.”. This workaround involves a SharePoint Online Management Shell cmdlet, using version 16.0.7918.1200 or better.

    Full details are on Microsoft Tech Community

  • Patch Lady – Bitlocker on 1803 pauses during updates

    Posted on August 16th, 2018 at 20:44 Susan Bradley Comment on the AskWoody Lounge

    The symptoms are:

    Windows 10 on 1803

    Bitlocker enabled on a computer without a TPM

    Bitlocker is enabled with a password/phrase

    During the installation of updates Bitlocker will get paused and have to be reenabled.

    No resolution at this time – just know that you aren’t alone.

  • R.I.P. Miss Aretha Franklin

    Posted on August 16th, 2018 at 14:28 Kirsty Comment on the AskWoody Lounge

    Very sad news today of the passing of The Queen of Soul.

    My favorites, her rendition of Carole King’s Natural Woman, and her performance in The Blues Brothers. You’ll probably have your own favorites, from her extensive catalog of work.

    May she rest in peace.


  • Having trouble logging in to Office 365? You aren’t alone.

    Posted on August 16th, 2018 at 11:51 woody Comment on the AskWoody Lounge

    The official @Office365Status account on Twitter says:

    There are several possible suspects listed in the linked thread. It seems that locally installed versions of Office 365 (as opposed to the web version) are causing problems. Possible that it’s associated with Modern Authentication. One user reports that he removed activation from his keychain and it worked.

  • Win10 1803 boot failure loop: bootres.dll is corrupt

    Posted on August 16th, 2018 at 10:43 woody Comment on the AskWoody Lounge

    This appears to be a general 1803 bug, not associated with any specific cumulative update.

    From @Dougcuk:

    There is recurring issue reported online where Win10 gets stuck in a repair loop. The Win10 Recovery Environment (RE) option Startup Repair fails to correct the problem. The Startup Repair log c:\windows\system32\logfiles\srt\SrtTrail.txt reports a fault:

    Root cause found:
    Boot critical file c:\efi\microsoft\boot\resources\custom\bootres.dll is corrupt.

    Repair action: File repair
    Result: Failed. Error code = 0x57

    The odd part of this error is the “Custom” folder location – this is not part of the normal folder structure. The bootres.dll file normally resides in the “Resources” folder with the BCD file in the folder above (Boot).

    What the error is reporting is that the bootres.dll file is missing (rather than corrupted) On the systems I have checked the “Custom” folder does NOT even exist – thus the bootres.dll cannot be present at this location and is declared “corrupt” by the Startup Repair utility.

    The bigger mystery is why the System thinks the file should be located in a “Custom” sub-folder in the first place. (Also I think the c: drive letter shown is an artifact – most likely it refers to the first partition – not the actual main C: drive – but that is a whole different can of worms)

    I am currently working on two HP laptops with this exact problem – both went down within an hour of each other. At first I though it must be a virus or malware attack gone wrong – but could find no evidence to support this idea.

    Having read multiple postings and responses across many different online forums: The evidence suggests this is a Microsoft bug that affects a limited number of Win10 systems. The problem appears to affect systems recently upgraded to version 1803 (only one case listed 1709 on a Surface device) – but only occurs after further updates (as yet unidentified) and then a full restart.

    I am exploring BCD repair and rebuild options with some success – but have no clean fix as yet (the standard RE repair options get lost)

    Anyone have any experience of this problem or ideas as to what causes this error?

  • Win10 1803 Aug cumulative update: Installation fail loop ”Update couldn’t apply, reverting changes”

    Posted on August 16th, 2018 at 10:28 woody Comment on the AskWoody Lounge

    Looks like this problem (which has occurred with every version of Win10, as far as I know) has reared its ugly head with the August Win10 1803 update.

    Uroboros4 on Reddit says:

    I have Win10 1803 genuine. None of the cumulative updates can be applied(for example KB4343909, kb4284835, kb4103721). It reaches 100% and says ” Update couldn’t apply, reverting changes”. I have tried a lot of stuff (pausing win update and manually installing them, scan windows for corrupted files to no avail). Anyone has the same problem?

  • Server 2016: Is the sysvol sync bug in July showing up in August?

    Posted on August 16th, 2018 at 07:47 woody Comment on the AskWoody Lounge

    From @njmalm1:

    Has anyone else experienced their GPOs not syncing permissions after applying KB4338814 to Server 2016?

    We were getting the ACL error

    “The sysvol permissions for one or more GPOs on this domain controller are not in sync with the permissions for the GPOs on the baseline domain”.

    Went through an Non-authoritative SYSVOL restore, demoting and promoting a domain controller, and finally uninstalled patch KB4338814 to resolve the issue.

    This problem existed on our test domain (two DCs 2012 and 2016) and our production (three DCs 1-2012 and 2-2016) The ACL sync issues only happened on one of the production 2016 DCs which was strange. Once we removed the patch we had to go to any GPOs still showing ACL errors and restore the delegation permissions to defaults in order for it to start syncing.

    I have blocked patch KB4338814 from July in WSUS but the issue is now happening again in our test Active Directory after applying the August cumulative updates. I’d love to know if anyone else is seeing this issue and if Microsoft has reported it as a problem.

  • Use Google Drive? Upgrade to Google One — cheap

    Posted on August 16th, 2018 at 07:37 Kirsty Comment on the AskWoody Lounge

    If you have a paid Google Drive account, you may have been upgraded already.

    Google One plans will start at 100 GB for US$1.99, 200 GB for US$2.99, and 2 TB for US$9.99 per month, while pricing for plans larger than 2TB will remain the same. (Existing 1 TB Drive plans will be upgraded to 2 TB at no extra cost.)

    Details in the comments.

    P.S. If you prefer OneDrive, Ed Bott has a handful of tricks you should consider in his ZDNet article.