|
|
Post by alanrwood on May 15, 2019 8:54:55 GMT
It has been reported widely that KB4494441 (Cumulative Update) leaves the version at 17763.475 ie it has not updated correctly. After the update it would be wise to check the version using Run/Winver. If the version has not changed try a repeat of Windows Update. On my machine it redownloaded this update and re-installed it. The version then changed to 17763.503. Strange as looking at the Update record it shows this update as being successful on both occasions.
|
|
|
|
Post by jal on May 15, 2019 11:23:04 GMT
Hi Alan
Does the last (2) in brackets at the end mean it updated twice.
2019-05 Comulative Update For Windows 10 Version 1809 for x64-based Systems (KB449441) (2)
Successfully Installed
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 15, 2019 13:31:52 GMT
It has been reported widely that KB4494441 (Cumulative Update) leaves the version at 17763.475 ie it has not updated correctly. After the update it would be wise to check the version using Run/Winver. If the version has not changed try a repeat of Windows Update. On my machine it redownloaded this update and re-installed it. The version then changed to 17763.503. Strange as looking at the Update record it shows this update as being successful on both occasions. Yes, I found that as well. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 15, 2019 13:42:25 GMT
|
|
|
|
Post by nob on May 15, 2019 14:13:52 GMT
It has been reported widely that KB4494441 (Cumulative Update) leaves the version at 17763.475 ie it has not updated correctly. After the update it would be wise to check the version using Run/Winver. If the version has not changed try a repeat of Windows Update. On my machine it redownloaded this update and re-installed it. The version then changed to 17763.503. Strange as looking at the Update record it shows this update as being successful on both occasions. Same for me, the only difference after manually downloading the update from M$ store and installing is an entry in update history above the cumulative update and that's security update with the same number. Thanks for the heads up Alan I wouldn't have noticed the number not changing. |
|
|
|
Post by jal on May 15, 2019 20:41:58 GMT
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 16, 2019 6:30:29 GMT
The latest version (of mine) is 17763.503.
|
|
|
|
Post by alanrwood on May 16, 2019 7:58:44 GMT
It appears that the update needs a .net update first in order to install. This is done on the first execution then the main update is installed on the second.
|
|
|
|
Post by nob on May 17, 2019 12:39:17 GMT
After the update some users Photo app stopped opening Jpegs it showed TWINUI as the opening app. When the photo app was tried it showed a reg error. Had that to sort out with the help of Windows Powershell.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 18, 2019 18:47:08 GMT
After the update some users Photo app stopped opening Jpegs it showed TWINUI as the opening app. When the photo app was tried it showed a reg error. Had that to sort out with the help of Windows Powershell. I haven't personally found that. |
|
|
|
Post by nob on May 19, 2019 7:30:08 GMT
After the update some users Photo app stopped opening Jpegs it showed TWINUI as the opening app. When the photo app was tried it showed a reg error. Had that to sort out with the help of Windows Powershell. I haven't personally found that. It wasn't my account it was other people who use the computer. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 19, 2019 7:32:41 GMT
I haven't personally found that. It wasn't my account it was other people who use the computer.  |
|
|
|
Post by nob on May 19, 2019 7:36:33 GMT
It wasn't my account it was other people who use the computer. They couldn't open Jpegs with Photos app, when tried they got the Registry error and TWINUI in the open with box. all other photo apps were fine. Mine opened and still do with Photos. Open a Jpeg and look what opens it Matt. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 19, 2019 7:44:21 GMT
OK, just tried one and as before, Photos app successfully opened it.
Anyway, not going to be around for a while, but I'll be around later.
|
|
|
|
Post by alanrwood on May 19, 2019 8:57:56 GMT
It seems Microsoft have now fixed the bug that made a second install necessary.
|
|
