Windows 10 Insider Preview (RS3) Build 16184 for PC released on Fast Ring
Saturday, April 29, 2017
Windows 10 for arm-based Phone Devices 10.0.15063.251 released on release preview
My "unsupported" phone Nokia Lumia 636 which is on "release preview" channel, it receive the update .251
After apply the update, there are some privacy setting show up for your selection
Windows 10 for arm-based Phone Devices 10.0.15063.251 released on release preview
Wednesday, April 26, 2017
Samsung Galaxy Note 4 (SM-N910U) release security update (Mar-2017)
The Note 4 SM-N910U release monthly security update and the latest version is 2017-3-1.
Samsung Galaxy Note 4 (SM-N910U) release security update (Mar-2017)
Labels:
Android Security Update,
Note 4
Thursday, April 20, 2017
Tuesday, April 18, 2017
Windows 7 - Windows Update error 80234004 solution
Solution - Install the following hotfix (Update for Windows 7 for x64-based Systems (KB3172605)) and reboot the computer
https://www.microsoft.com/en-us/download/details.aspx?id=53332
Then, I able to run Windows update successfully to apply those missing patches.
Remark:
To apply this update, you must install Service Pack 1 for Windows 7 or Windows Server 2008 R2 and April 2015 servicing stack update for Windows 7 and Windows Server 2008 R2 .
In my case, I also apply Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1 before and also, my machine last windows update is 19 July 2016. (After that, I did not turn on the machine until today)
Windows 7 - Windows Update error 80234004 solution
Labels:
Windows 7,
Windows Update
Saturday, April 15, 2017
Windows 10 Insider Preview (RS3) Build 16176 for PC and Build 15204 for Mobile released on Fast Ring
The PC build are going to PC and tablet now, since my mobile Nokia Lumia 636 no longer being support.....I cannot test the RS3 on my mobile.....not sure should I buy a new Windows Phone for production and change my 640 to become testing machine.......
Reference:
Windows 10 Insider Preview (RS3) Build 16176 for PC and Build 15204 for Mobile released on Fast Ring
Labels:
Insider Preview,
RS3,
Windows 10,
Windows 10 for mobile
Thursday, April 13, 2017
Windows 10 for mobile creators update (15063) second CU (138) released
The update description have been changed to Windows 10 for am-based Phone Devices... and also it is specific which is a April update
Windows 10 for mobile creators update (15063) second CU (138) released
Windows 10 Mobile (14393.1066) update released
It is a good update which is improve the overall performance on my Nokia Lumia 640.
Windows 10 Mobile (14393.1066) update released
Labels:
Cumulative Update,
Windows 10 for mobile
Monday, April 10, 2017
How to upgrade the Chuwi Vi8 Plus BIOS?
The tablet BIOS is running on P03_C806.108
1. Go to download the latest Chuwi Vi8 Plus BIOS:
https://mega.nz/#!ZhZEGbAR!nU3qq ... aZvzuRQ4eXNNTtMoKG8
http://forum.chuwi.com/thread-1175-1-1.html
2. Run the P03_C806.rom.exe
3. Waiting for the command prompt disappear
4. Reboot the machine
5. Done
How to upgrade the Chuwi Vi8 Plus BIOS?
Labels:
BIOS,
Chuwi Vi8 Plus,
Upgrade
Saturday, April 8, 2017
Windows 10 Insider Preview (RS3) Build 16170 for PC released on Fast Ring
The first insider preview for code name: RedStone 3 (RS3) have been released on Fast Ring.
Windows 10 Insider Preview (RS3) Build 16170 for PC released on Fast Ring
Labels:
RS3,
Windows 10,
Windows Insider
Friday, April 7, 2017
Upgrade my production machine - WMP EHCTF801 to Windows 10 (1703) Creators Update via Windows Update Assistant
I just cannot wait for 11 April, so I use the Windows Update Assistant method to manual upgrade my production machine.
1. Go to https://www.microsoft.com/en-hk/software-download/windows10 download the Windows Update Assistant
2. Click the "Update Now"
3. After you pass the compatibility check, you will see a screen like the following: (Make sure you make a backup before, check your antivirus compatibility and also connect the AC power)
4. After reboot and the upgrade complete, you machine will running on 15063.13
After the upgrade, the performance of the machine have been improved.
Reference:
http://www.redmondpie.com/download-windows-10-update-assistant-for-creators-update/
Upgrade my production machine - WMP EHCTF801 to Windows 10 (1703) Creators Update via Windows Update Assistant
McAfee VirusScan Enterprise 8.8 user preparation before upgrade to Windows 10 (1703) Creators Update (15063)
McAfee VirusScan Enterprise 8.8 user need to upgrade to patch 9 and McAfee agent 5.0.5 before upgrade to Windows 10 (1703) Creators Update (15063)
Steps:
1. Apply 8.8 patch 9 (8.8.0.1804)
2. Upgrade McAfee agent (MA) to 5.0.5 (5.0.5.658)
3. Start the Windows 10 upgrade
Reference:
https://kc.mcafee.com/corporate/index?page=content&id=kb51111
McAfee VirusScan Enterprise 8.8 user preparation before upgrade to Windows 10 (1703) Creators Update (15063)
Labels:
Creators Update,
McAfee,
Windows 10
Tuesday, April 4, 2017
Google Chrome cannot access any https:\\ website and the return error is "Your connection is not private" (NET:ERR_CERT_WEAK_SIGNATURE_ALGORITHM)
Problem:
Google Chrome cannot access any https:\\ website and the return error is "Your connection is not private" (NET:ERR_CERT_WEAK_SIGNATURE_ALGORITHM)
Affected Users:
Users who is new install Google Chrome v.56 or above (Existing user who have chrome installed and upgrade to v.56 or above did not affected)
Reason:
Proxy CA certificate still using SHA-1, it cause Google Chrome did not allow all https:\\ website access due to it remove support for SHA-1 certificate.
Workaround Solution:
Create a registry key:
EnableSha1ForLocalAnchors and Value = 1
Whether SHA-1 signed certificates issued by local trust anchors are allowed
Data type:
Boolean [Windows:REG_DWORD]
Windows registry location:
HKLM\Software\Policies\Google\Chrome\EnableSha1ForLocalAnchors
Remark:
When this setting is enabled, Google Chrome allows SHA-1 signed certificates as long as they successfully validate and chain to a locally-installed CA certificates.
Note that this policy depends on the operating system certificate verification stack allowing SHA-1 signatures. If an OS update changes the OS handling of SHA-1 certificates, this policy may no longer have effect. Further, this policy is intended as a temporary workaround to give enterprises more time to move away from SHA-1. This policy will be removed on or around January 1st 2019.
Issue fixed:
Reference:
https://productforums.google.com/forum/#!topic/chrome/nIHIV7DGBPc;context-place=topicsearchin/chrome/category$3ACanary%7Csort:relevance%7Cspell:false
https://www.reddit.com/r/networking/comments/60h4h1/bluecoat_proxy_and_chrome_57/?st=j11gnmvm&sh=bb196a17
https://threatpost.com/google-removing-sha-1-support-in-chrome-56/122041/
https://blog.gslin.org/archives/2016/11/21/6961/google-chrome-%E5%B0%87%E5%9C%A8-2017-%E7%9A%84-56-%E7%89%88%E5%81%9C%E6%AD%A2%E6%94%AF%E6%8F%B4-sha-1-ssl-certificate/
http://winintro.com/?Category=Chrome&Policy=Google.Policies.Chrome%3A%3AEnableSha1ForLocalAnchors
https://security.googleblog.com/2016/11/sha-1-certificates-in-chrome.html
https://www.chromium.org/administrators/policy-list-3#EnableSha1ForLocalAnchors
An update to our SHA-1 deprecation roadmap
Read more at https://blogs.windows.com/msedgedev/2016/04/29/sha1-deprecation-roadmap/#botVpEml4p81z0Vy.99
Google Chrome cannot access any https:\\ website and the return error is "Your connection is not private" (NET:ERR_CERT_WEAK_SIGNATURE_ALGORITHM)
Labels:
deprecation,
Google Chrome,
SHA-1,
SSL Certificate
Sunday, April 2, 2017
How to resolve the symbol in command prompt become "Yen" dollar on Win 10 (1607) when set locale to "Chinese (Traditional, Hong Kong SAR) without using Windows Update?
Problem: The symbol in command prompt become "Yen" dollar when we set our locale to "Chinese (Traditional, Hong Kong SAR)" since the command prompt using "MS Gothic" which is Japanese Supplemental Fonts
The reason of using "MS Gothic" seems to be the machine is missing Chinese (Traditional) Supplemental Fonts: DFKai-SB, MingLiU, MingLiU_HKSCS, PMingLiU (We do the same configuration on other machine which is request us to download "Chinese (Traditional) Supplemental Fonts", since the problematic machine have been disable Windows Update, it did not request to download.)
Solution: Since the Windows Update have been disabled or managed by WSUS
We need to download the "Features on Demand" and "Language pack" and install them locally (Offline)
We able to download the Features on Demand for 1607 only but not the Language pack for 1607 from VLSC
But we found the direct download http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/07/lp_09c06c2907d6ecb5becd01178563808bef832e7b.cab
Command use:
Install Chinese Traditional - Language pack zh-TW (Remark: zh-HK on 1607 is no longer exist, using the zh-TW is same as zh-HK on 1607)
DISM.EXE /Online /Add-Package /PackagePath:C:\Source\lp_09c06c2907d6ecb5becd01178563808bef832e7b.cab
Install Chinese Traditional Fonts
DISM.EXE /Online /Add-Package /PackagePath:D:\Microsoft-Windows-LanguageFeatures-Fonts-Hant-Package.cab
Issue resolved:
Reference:
https://answers.microsoft.com/en-us/windows/forum/windows_10-start/some-fonts-are-missing-after-upgrade/95839dfa-0df2-4bc0-875a-fd6b57e61fe4
http://www.ms-labrats.de/2015/11/fonts-are-missing-after-windows-10.html
http://superuser.com/questions/1121323/windows-10-chinese-traditional-language-option-differences
http://www.thewindowsclub.com/install-uninstall-languages-windows-10
https://answers.microsoft.com/en-us/windows/forum/windows_10-start/some-fonts-are-missing-after-upgrade/95839dfa-0df2-4bc0-875a-fd6b57e61fe4
https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/features-on-demand-v2--capabilities
http://stackoverflow.com/questions/37233889/how-to-add-windows-10-optional-fonts-programmatically
https://superuser.com/questions/870864/how-to-run-dism-against-a-local-source
https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/dism-image-management-command-line-options-s14
How to resolve the symbol in command prompt become "Yen" dollar on Win 10 (1607) when set locale to "Chinese (Traditional, Hong Kong SAR) without using Windows Update?
Labels:
Anniversary Update,
Windows 10
Saturday, April 1, 2017
How to upgrade a current branch (CB) Windows 10 1607 to Windows 10 1703 by using Windows 10 Insider Preview Advanced ISO? To upgrade to 1703 (15063) before 11 Apr 2017
I test the following method on two Windows 10 1607 CB 14393.x machines successfully (Remark: Please make a backup before upgrade)
Step 1: Go to https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced (You need to use you Windows Insider account login to download the ISO)
Step 2: Double click on the ISO file and run the "setup.exe"
Step 3: Follow the wizards:
After the upgrade complete, you will found that your machine to become Windows 10 1703 (15063)
How to upgrade a current branch (CB) Windows 10 1607 to Windows 10 1703 by using Windows 10 Insider Preview Advanced ISO? To upgrade to 1703 (15063) before 11 Apr 2017
Labels:
Creators Update,
Insider Preview,
Windows 10
Subscribe to:
Posts (Atom)