本文的目的是介绍EKOffers促销微软软件：可1折买下Windows10Pro的详细情况，特别关注微软商店促销的相关信息。我们将通过专业的研究、有关数据的分析等多种方式，为您呈现一个全面的了解EKO
本文的目的是介绍EKOffers促销微软软件：可1折买下Windows 10 Pro的详细情况，特别关注微软商店促销的相关信息。我们将通过专业的研究、有关数据的分析等多种方式，为您呈现一个全面的了解EKOffers促销微软软件：可1折买下Windows 10 Pro的机会，同时也不会遗漏关于Kube-Proxy-Windows CrashLoopBackOff 主节点Windows 工作节点、Microsoft shows off how containerized apps will work in Windows 10X、Microsoft: This is how Windows 10 has been changed by Windows Insider feedback、Microsoft现在向Windows10添加Windows 10X功能的知识。
本文目录一览：- EKOffers促销微软软件：可1折买下Windows 10 Pro（微软商店促销）
- Kube-Proxy-Windows CrashLoopBackOff 主节点Windows 工作节点
- Microsoft shows off how containerized apps will work in Windows 10X
- Microsoft: This is how Windows 10 has been changed by Windows Insider feedback
- Microsoft现在向Windows10添加Windows 10X功能
EKOffers促销微软软件：可1折买下Windows 10 Pro（微软商店促销）
2月25日，据外媒报道，国外导购网站EKOffers为自家销售的Windows 10 Pro密匙拿出了令人瞩目的低价——14.88美元，约合人民币99元。微软官网售价199.99美元，约合人民币1337元，EKOffers给出的价格相当于正常价格的1折还要低。网站称该密匙全球有效，可以通过电话激活。
除此之外，EKOffers还以41.38美元的价格销售Office 2016 Professional Plus，约合人民币270元，官方原价283.02美元，约合人民币1890元，EKOffers给出的价格相当于正常价格的2折还要低。
EKOffers还给出了Win10+Office套餐，两款产品一起买售价51.41美元（可节省4.85美元），约合人民币340元。
当然这么便宜也是有原因的，EKOffers在商品页解释了售卖的Windows 10 Pro密匙是OEM PC CD Key。
从商品页面来看，这两件商品尚不限量，各位读者可以按需购买哦。
Kube-Proxy-Windows CrashLoopBackOff 主节点Windows 工作节点
如何解决Kube-Proxy-Windows CrashLoopBackOff 主节点Windows 工作节点？
安装过程
我是 Kubernetes 的新手，目前正在 Azure VM 内设置 Kubernetes 集群。我想部署 Windows 容器，但为了实现这一点，我需要添加 Windows 工作节点。我已经部署了一个带有 3 个主节点和一个 Linux 工作节点的 Kubeadm 集群，这些节点运行良好。
一旦我添加了 Windows 节点，一切都会下降。首先，我使用 Flannel 作为我的 CNI 插件，并根据 Kubernetes 文档准备 deamonset 和控制平面：https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/
然后在安装了 Flannel deamonset 之后，我相应地安装了代理和 Docker EE。
使用过的软件
主节点
操作系统：Ubuntu 18.04 LTS
容器运行时：Docker 20.10.5
Kubernetes 版本：1.21.0
法兰绒图像版本：0.14.0
Kube-代理版本：1.21.0
Windows 工作节点
操作系统：Windows Server 2019 数据中心核心
容器运行时：Docker 20.10.4
Kubernetes 版本：1.21.0
法兰绒镜像版本：0.13.0-nanoserver
Kube-proxy 版本：1.21.0-nanoserver
想要的结果：
我希望看到一个完整的集群可以使用，并且在 Running 状态下拥有所有需要的东西。
当前结果：
安装后我检查是否安装成功：
azureuser@Kube-M-001:~$ kubectl get pods -o wide -n kube-system
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READInesS GATES
coredns-558bd4d5db-8mshg 1/1 Running 0 178m 10.244.0.3 kube-m-001 <none> <none>
coredns-558bd4d5db-xhsmn 1/1 Running 0 178m 10.244.0.2 kube-m-001 <none> <none>
etcd-kube-m-001 1/1 Running 0 178m 10.0.10.4 kube-m-001 <none> <none>
etcd-kube-m-002 1/1 Running 0 164m 10.0.10.5 kube-m-002 <none> <none>
etcd-kube-m-003 1/1 Running 0 162m 10.0.10.6 kube-m-003 <none> <none>
kube-apiserver-kube-m-001 1/1 Running 0 178m 10.0.10.4 kube-m-001 <none> <none>
kube-apiserver-kube-m-002 1/1 Running 1 165m 10.0.10.5 kube-m-002 <none> <none>
kube-apiserver-kube-m-003 1/1 Running 0 162m 10.0.10.6 kube-m-003 <none> <none>
kube-controller-manager-kube-m-001 1/1 Running 1 178m 10.0.10.4 kube-m-001 <none> <none>
kube-controller-manager-kube-m-002 1/1 Running 0 165m 10.0.10.5 kube-m-002 <none> <none>
kube-controller-manager-kube-m-003 1/1 Running 0 163m 10.0.10.6 kube-m-003 <none> <none>
kube-flannel-ds-5lwzf 1/1 Running 0 165m 10.0.10.5 kube-m-002 <none> <none>
kube-flannel-ds-6lvgp 1/1 Running 0 129m 10.0.10.7 kube-w-001 <none> <none>
kube-flannel-ds-dlmkt 1/1 Running 0 163m 10.0.10.6 kube-m-003 <none> <none>
kube-flannel-ds-h27r7 1/1 Running 0 169m 10.0.10.4 kube-m-001 <none> <none>
kube-flannel-ds-windows-amd64-hwbjc 1/1 Running 0 121m 10.0.64.4 kube-w-002 <none> <none>
kube-proxy-4rkgk 1/1 Running 0 178m 10.0.10.4 kube-m-001 <none> <none>
kube-proxy-6g4sb 1/1 Running 0 129m 10.0.10.7 kube-w-001 <none> <none>
kube-proxy-tvm9g 1/1 Running 0 165m 10.0.10.5 kube-m-002 <none> <none>
kube-proxy-windows-j7c27 0/1 CrashLoopBackOff 26 121m 10.244.4.2 kube-w-002 <none> <none>
kube-proxy-wzjm7 1/1 Running 0 163m 10.0.10.6 kube-m-003 <none> <none>
kube-scheduler-kube-m-001 1/1 Running 1 178m 10.0.10.4 kube-m-001 <none> <none>
kube-scheduler-kube-m-002 1/1 Running 0 165m 10.0.10.5 kube-m-002 <none> <none>
kube-scheduler-kube-m-003 1/1 Running 0 162m 10.0.10.6 kube-m-003 <none> <none>
我查看了特定 kube-proxy pod 的日志，得到以下结果：
azureuser@Kube-M-001:~$ kubectl logs -n kube-system kube-proxy-windows-j7c27 -p
Directory: C:\host\var\lib\kube-proxy\var\run\secrets\kubernetes.io
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 12:08 PM serviceaccount
Directory: C:\host\k
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 12:24 PM kube-proxy
Using CNI conf file: 10-flannel.conf
I0503 12:30:23.146002 2448 flags.go:59] FLAG: --add-dir-header="false"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --alsologtostderr="false"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --bind-address="0.0.0.0"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --bind-address-hard-fail="false"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --cleanup="false"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --cluster-cidr=""
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --config="/var/lib/kube-proxy/config.conf"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --config-sync-period="15m0s"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --conntrack-max-per-core="32768"
I0503 12:30:23.194891 2448 flags.go:59] FLAG: --conntrack-min="131072"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --conntrack-tcp-timeout-close-wait="1h0m0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --conntrack-tcp-timeout-established="24h0m0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --detect-local-mode=""
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --enable-dsr="false"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --feature-gates="WinOverlay=true"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --healthz-bind-address="0.0.0.0:10256"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --healthz-port="10256"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --help="false"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --hostname-override="kube-w-002"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --iptables-masquerade-bit="14"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --iptables-min-sync-period="1s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --iptables-sync-period="30s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-exclude-cidrs="[]"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-min-sync-period="0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-scheduler=""
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-strict-arp="false"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-sync-period="30s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-tcp-timeout="0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-tcpfin-timeout="0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --ipvs-udp-timeout="0s"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --kube-api-burst="10"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --kube-api-content-type="application/vnd.kubernetes.protobuf"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --kube-api-qps="5"
I0503 12:30:23.195318 2448 flags.go:59] FLAG: --kubeconfig=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --log-backtrace-at=":0"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --log-dir=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --log-file=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --log-file-max-size="1800"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --log-flush-frequency="5s"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --logtostderr="true"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --masquerade-all="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --master=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --metrics-bind-address="127.0.0.1:10249"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --metrics-port="10249"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --network-name=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --nodeport-addresses="[]"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --one-output="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --oom-score-adj="-999"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --profiling="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --proxy-mode=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --proxy-port-range=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --show-hidden-metrics-for-version=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --skip-headers="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --skip-log-headers="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --source-vip=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --stderrthreshold="2"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --udp-timeout="250ms"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --v="6"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --version="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --vmodule=""
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --windows-service="false"
I0503 12:30:23.195454 2448 flags.go:59] FLAG: --write-config-to=""
I0503 12:30:23.197789 2448 feature_gate.go:243] feature gates: &{map[WinOverlay:true]}
I0503 12:30:23.197789 2448 feature_gate.go:243] feature gates: &{map[WinOverlay:true]}
I0503 12:30:23.200622 2448 loader.go:372] Config loaded from file: /var/lib/kube-proxy/kubeconfig.conf
I0503 12:30:23.221725 2448 server_windows.go:107] Using Kernelspace Proxier.
I0503 12:30:23.221725 2448 server_windows.go:110] creating dualStackProxier for Windows kernel.
time="2021-05-03T12:30:23Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,12"
time="2021-05-03T12:30:23Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,10"
time="2021-05-03T12:30:23Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,13"
time="2021-05-03T12:30:23Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,10"
I0503 12:30:23.224600 2448 proxier.go:562] "Cleaning up old HNS policy lists"
I0503 12:30:33.229568 2448 proxier.go:583] "Hns Network loaded" hnsNetworkInfo=&{name:flannel.4096 id:ae948621-bb34-486d-b31d-cf397757b7c1 networkType:Overlay remotesubnets:[0xc0000b77c0 0xc0000b7840 0xc0000b78c0 0xc0000b7940]}
time="2021-05-03T12:30:33Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,12"
time="2021-05-03T12:30:33Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,10"
time="2021-05-03T12:30:33Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,13"
time="2021-05-03T12:30:33Z" level=info msg="currentVersion.Major < versionRange.MinVersion.Major: 9,10"
F0503 12:30:33.256757 2448 server.go:489] unable to create proxier: unable to create ipv4 proxier: Could not find host mac address for 0.0.0.0,hostname: kube-w-002,clusterCIDR : 10.244.0.0/16,nodeIP:0.0.0.0
但我认为 Flannel 安装中已经出了问题，因为 Flannel pod 的日志给出了以下结果：
PS C:\Users\azureuser> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0cfa1c0c7b6d mcr.microsoft.com/oss/kubernetes/pause:1.4.1 "cmd /S /C pauseloop…" 2 hours ago Up 2 hours k8s_POD_kube-proxy-windows-j7c27_kube-system_df8fda84-cf94-4ca7-863a-9c9694f2b3ba_8
fb3ccc5e0cf7 sigwindowstools/flannel "pwsh -file /etc/kub…" 2 hours ago Up 2 hours k8s_kube-flannel_kube-flannel-ds-windows-amd64-hwbjc_kube-system_9f0aa635-200b-4902-93cc-1d1da7f49a5d_0
bc8e97427613 mcr.microsoft.com/oss/kubernetes/pause:1.4.1 "cmd /S /C pauseloop…" 2 hours ago Up 2 hours k8s_POD_kube-flannel-ds-windows-amd64-hwbjc_kube-system_9f0aa635-200b-4902-93cc-1d1da7f49a5d_0
PS C:\Users\azureuser> docker logs fb3ccc5e0cf7
Directory: C:\host\etc\cni
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 10:28 AM net.d
Directory: C:\host\etc
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 10:28 AM kube-flannel
Directory: C:\host\opt\cni
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 10:28 AM bin
Directory: C:\host\k
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 10:28 AM flannel
Directory: C:\host\k\flannel\var\run\secrets\kubernetes.io
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 5/3/2021 10:28 AM serviceaccount
Configuring CNI for docker
WARNING: The names of some imported commands from the module ''hns'' include unapproved verbs that might make them less
discoverable. To find the commands with unapproved verbs,run the Import-Module command again with the Verbose
parameter. For a list of approved verbs,type Get-Verb.
Invoke-HnsRequest : @{Error=An adapter was not found. ; ErrorCode=2151350278; Success=False}
At C:\k\flannel\hns.psm1:233 char:16
+ ... return Invoke-HnsRequest -Method POST -Type networks -Data $Json ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error],WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-HNSRequest
FATA[2021-05-03T10:28:44Z] rpc error: code = Internal desc = Could not create IP forward entry: The object already exists.
I0503 10:28:45.340006 5512 main.go:518] Determining IP address of default interface
I0503 10:28:47.695146 5512 main.go:531] Using interface with name Ethernet 2 and address 10.0.64.4
I0503 10:28:47.695146 5512 main.go:548] Defaulting external address to interface address (10.0.64.4)
I0503 10:28:47.767526 5512 kube.go:119] Waiting 10m0s for node controller to sync
I0503 10:28:47.769102 5512 kube.go:306] Starting kube subnet manager
I0503 10:28:48.769283 5512 kube.go:126] Node controller sync successful
I0503 10:28:48.769283 5512 main.go:246] Created subnet manager: Kubernetes subnet Manager - kube-w-002
I0503 10:28:48.769283 5512 main.go:249] Installing signal handlers
I0503 10:28:48.769283 5512 main.go:390] Found network config - Backend type: vxlan
I0503 10:28:48.769283 5512 vxlan_windows.go:127] VXLAN config: Name=flannel.4096 MacPrefix=0E-2A VNI=4096 Port=4789 GBP=false DirectRouting=false
I0503 10:28:48.838521 5512 device_windows.go:115] Attempting to create HostComputeNetwork &{ flannel.4096 Overlay [] {[]} { [] [] []} [{Static [{10.244.4.0/24 [[123 34 84 121 112 101 34 58 34 86 83 73 68 34 44 34 83 101 116 116 105 110 103 115 34 58 123 34 73 115 111 108 97 116 105 111 110 73 100 34 58 52 48 57 54 125 125]] [{10.244.4.1 0.0.0.0/0 0}]}]}] 8 {2 0}}
E0503 10:28:49.279614 5512 streamwatcher.go:109] Unable to decode an event from the watch stream: read tcp 10.0.64.4:50315-><PUBLIC-IP>:6443: wsarecv: An established connection was aborted by the software in your host machine.
E0503 10:28:49.323566 5512 reflector.go:304] github.com/coreos/flannel/subnet/kube/kube.go:307: Failed to watch *v1.Node: Get "https://kube-lb.eastus.cloudapp.azure.com:6443/api/v1/nodes?resourceVersion=6092&timeoutSeconds=582&watch=true": dial tcp: lookup kube-lb.eastus.cloudapp.azure.com: no such host
I0503 10:28:53.739453 5512 device_windows.go:123] Waiting to get ManagementIP from HostComputeNetwork flannel.4096
I0503 10:28:54.248878 5512 device_windows.go:134] Waiting to get net interface for HostComputeNetwork flannel.4096 (10.0.64.4)
I0503 10:28:54.758966 5512 device_windows.go:148] Created HostComputeNetwork flannel.4096
I0503 10:28:54.804770 5512 main.go:313] Changing default FORWARD chain policy to ACCEPT
I0503 10:28:54.816024 5512 main.go:321] Wrote subnet file to /run/flannel/subnet.env
I0503 10:28:54.816024 5512 main.go:325] Running backend.
I0503 10:28:54.816024 5512 main.go:343] Waiting for all goroutines to exit
I0503 10:28:54.816024 5512 vxlan_network_windows.go:63] Watching for new subnet leases
谁能帮帮我？所以我可以在 Kubernetes 集群中使用我的 Windows 工作节点。
编辑 1：
解决了 Flannel FATA 错误，此问题是由于 Flannel 无法识别网络适配器引起的。所以在我开始 Flannel 之前，我手动创建了所需的网络：
#First download HNS
PS C:\Users\azureuser> curl.exe -LO https://raw.githubusercontent.com/microsoft/SDN/master/Kubernetes/windows/hns.psm1
ipmo ./hns.psm1
#Create the network
PS C:\Users\azureuser> New-HNSNetwork -Type Overlay -Addressprefix "192.168.255.0/30" -Gateway "192.168.255.1" -Name "External" -AdapterName "Ethernet 2" -subnetPolicies @(@{Type = "VSID"; VSID = 9999; });
此后，您可以将 windows-node 加入集群，Flannel 将正常启动，但 Kube-proxy 问题仍然存在。
解决方法
您仍然遇到此错误吗？我设法通过将 windows kube-proxy 降级到至少 1.20.0 来解决这个问题。 1.21.0 肯定有一些配置缺失或错误。
curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed ''s/VERSION/v1.20.0/g'' | kubectl apply -f -
Microsoft shows off how containerized apps will work in Windows 10X
http://www.zdnet.com/article/microsoft-shows-off-how-containerized-apps-will-work-in-windows-10x/
Credit: Microsoft
Windows 10
- Now that Windows 7 support has ended, your business has four options
- Revived Windows 95 PowerToys lets you create Windows 10 keyboard shortcuts
- Microsoft to combine its Windows client and hardware teams under Chief Product Officer Panos Panay
- Best laptop deals: Windows and Chromebooks for under $500 (CNET)
- Microsoft Teams: A cheat sheet (TechRepublic Premium)
Microsoft is continuing to unfurl its dual-screen Windows and Android device story. On February 11, Microsoft is focusing primarily on the Windows piece of its strategy, making available its promised Windows 10X emulator and software development kit (SDK) for dual-screen Windows devices like its coming Surface Neo dual-screen tablet and various third-party foldables and new form factors.
Microsoft initially took the public wraps off Windows 10X, a variant of Windows 10 initially targeted for dual-screen devices, in October 2019, though leaks about its so-called "Santorini"/"Lite" platforms had been circulating for the last couple of years. On February 11, during its Microsoft 365 Developer Day virtual event, Microsoft is providing more details on what 10X is and how it will work.
As rumored for months, containers are a key to the 10X platform.
Microsoft is planning to require every Windows 10X app -- Win32, Universal Windows Platform (UWP) and Web apps -- to run in containers as a way to better secure and improve the performance of devices running Windows 10X. The 10X container (codenamed "Vail") is similar to -- though not the same as -- the lightweight VMs/container model used by Microsoft''s Windows Subsystem for Linux. The 10X container will include a lightweight version of Windows (Win32), which will be loaded only by those apps which require it. In some cases, shims, or programming interfaces meant to assist with compatibility, also will play a role in enabling apps like the new Edge browser and Microsoft''s own Office apps, to run on 10X.
Update: Thanks to a presentation discovered by The Walking Cat, here''s some more 10X container info. There are three types of containers in Windows 10X: Win32, MSIX and Native (UWP). MSIX and native containers already exist. Win32 containers are meant to provide the highest compatibility levels for existing apps, including Win32, WinForms, WPF and Electron apps. It provides an environment similar to a desktop OS. A single Win32 container will run all Win32 apps on 10X.
Microsoft''s goal is to ensure that most existing Windows applications will "just work" with no developer modifications required, on Windows 10X. For developers who are interested in making their applications work better and in a more customized way on 10X, Microsoft is making available the programming interfaces, information about hinge positions, transitions and new proposed Web standards in that space.
In addition to releasing early versions of the 10X emulator and SDK today, Microsoft also is refreshing the already-available SDK for its Android-based Surface Duo device. The preview SDK for Duo, as of today, will include all of Microsoft''s Java native samples as Kotlin samples; drag and drop support for helping with moving data between two apps on dual-screen devices; and support for Android Sutdio, Visual Studio and Visual Studio Code users on macOS and Ubuntu Linux and Windows.
While the smaller Duo (which Microsoft doesn''t want users to call a phone, but which will have telephony capabilities) and the larger dual-screen Neo will run different operating systems underneath, Microsoft is trying to emphasize the commonalities of the two platforms. Microsoft is touting its dual-screen SDK for Xamarin Forms as a tool for building apps across both Windows 10X and Android, for example. And the user experiences on the Duo and Neo, in many ways, look more similar than different, at least to my non-design-noticing eye.
Microsoft''s pitch for both kinds of dual-screen devices isn''t just that more screen real estate is better. It also is trying to build a case that users can be more productive when using two side-by-side, connected screens than a single screen because they can stay in their "flow" and not have to switch between apps.
It''s not just on the use-case front where Microsoft has its work cut out for it with dual-screen devices. Microsoft also has some big execution challenges with its dual-screen devices is an understatement.
Microsoft has said both the Surface Duo and the Neo will be available for purchase in time for holiday 2020 and seems to be sticking with that commitment. This doesn''t seem like a stretch for the Surface Duo, which is basically a plain-vanilla Android device with some Microsoft extensions. The Duo emulator is the existing Android Studio emulator.
The Surface Neo, though a Windows 10 device using a Microsoft-built emulator, will be expected by most customers to run all Windows apps. I''ve heard that in its own internal testing so far, Microsoft has not found providing Win32 app compatibility to be a slam-dunk. Because the Win32 subsystem running in the container in 10X isn''t a full operating system implementation, more than a few existing Win32 apps don''t run well or at all.
In addition, Microsoft also is in the midst of trying to figure out what to do about app distribution. As I''ve reported previously, Microsoft has been stepping back from requiring Windows 10 apps to be delivered via the Microsoft app store. During today''s Microsoft 365 Developer Day, I''m not expecting Microsoft to talk about its plans to deprecate the Microsoft Store for Business and Store for Education.
However, there may be some talk today during the virtual developer event about how the company is devising a new model for application reputation, as officials hinted last year would be happening. Microsoft needs to build an app reputation system that will help customers know that apps are trustworthy and safe to download. Microsoft is expected to make this new app-reputation model a built-in part of Windows 10X and subsequently make it available across the entire ecosystem, from what I''ve heard.
Microsoft is looking for developer feedback on its dual-screen vision and deliverables, in earnest, starting today. Windows 10X testers, start your engines.
Microsoft: This is how Windows 10 has been changed by Windows Insider feedback
http://www.zdnet.com/article/microsoft-this-is-how-windows-10-has-been-changed-by-windows-insider-feedback/
Five years ago Microsoft''s switched from big-bang Windows releases every few years to Windows 10 twice-yearly updates. The company has now reflected on all the ways that feedback from fans has shaped Windows 10 during that period.
Windows 10
- The new Microsoft Edge: 10 rules to take control of your browser
- Windows 10 upgrade rush got us buying PCs again - but not for very long
- Windows 10 users: Google reveals when it''s killing off Chrome apps
- Best laptop deals: Windows and Chromebooks for under $500 (CNET)
- Windows 10: A cheat sheet (TechRepublic)
Ahead of the first Windows 10 release in 2015, Microsoft introduced the Windows Insider Program, which attracted one million Windows fans in 2014, grew to 10 million users by 2017, and in June last year had gained 16.5 million participants.
Windows Insiders are a small but influential army of Windows 10 fans who help shape the operating system that powers 900 million devices today.
In 2014, testers provided feedback via Microsoft''s near real-time telemetry system, codenamed ''Asimov'', which came from tools used in Xbox development processes. Back then, participants submitted complaints and opinions via the ''Windows Feedback app'', which these days is called the Feedback Hub.
After the disastrous Windows 10 version 1809 rollout, Microsoft has been honing the tool to ensure it doesn''t miss low-volume but high-impact bugs reported by insiders. The 1809 experience has led to massive changes in the how Microsoft approaches its twice-yearly major feature updates.
And late last year, Windows Insiders lost their ''Chief #NinjaCat'', Dona Sarkar, to another department at Microsoft.
So, lots has changed in the past five years and Microsoft this week paid tribute to the millions of Windows 10 insiders who''ve helped shape the OS in that time, highlighting the top features it gained thanks to Windows Insider feedback.
The first feature is emoji, kaomoji and symbols, which Windows Insiders from around the world wanted easier ways to type. Kaomoji – Japanese emoticons such as /ᐠ。ꞈ。ᐟ\ – were introduced in version Windows 10 version 1903, and in Windows 10 20H1 users gained more kaomoji options to share with friends.
The second is OneDrive Files On-Demand, which Microsoft finally released in 2017, three years after it first started testing it with Windows Insiders but then dropped before the first Windows 10 release.
The feature allowed users to access all files in the cloud without having to download them and consume local disk space.
"When you turn on this feature, you''ll see all your files in File Explorer. New files created online or on another device appear as online-only files, which don''t take up space on your device. When you''re connected to the internet, you''ll be able to use the files just like any other file on your device," Microsoft said today.
This feature helped shape Microsoft''s recent efforts to supercharge File Explorer with Windows Search, which now gives users local and web search results that appear on the fly in a drop-down menu. Unfortunately though, Windows 10 users complained that the new File Explorer Search Box was "completely unusable". Even with this week''s improvements, it''s still been branded a "crummy" experience.
Microsoft also addressed the Feedback Hub and Windows Insiders'' input that led to Collections, which tries to weed out duplicate reports and noise to focus on issues that matter.
"Collections bring similar feedback together in one place. The little stack of cards icon next to the feedback''s title shows it''s a collection, and we''re continuing to work on creating more collections as new feedback comes in," said Microsoft.
While Microsoft''s new features always attract complaints, the post highlights the many features where fan feedback has helped improve them.
Other major features Microsoft credits insiders with shaping include dark mode for Sticky Notes, the new Chromium-based Edge, system-wide ''night-light'' settings, the Windows Sandbox, the Windows Subsystem for Linux (WSL), and the new Windows Terminal for command-line users.
There are also dictation and text predictions, touchpad gestures, the Your Phone app, Notepad improvements, better screenshot capabilities, and the return of PowerToys.
If anything, the post illustrates Microsoft''s efforts to reshape itself in a world in which it lost the chance to dominate mobile, but remains a dominant force among developers and IT pros.
More on Microsoft and Windows 10 updates
Microsoft现在向Windows10添加Windows 10X功能
当微软在去年10月的Surface活动期间首次发布Windows 10 X时，微软将操作系统定位为专为双屏设备(例如其自己的Surface Neo)设计的软件。微软最近表示计划已经改变，Windows 10 X将首先用于单屏笔记本电脑。
5月下旬，我们独家报道了Microsoft将在Windows10中添加一些Windows 10 X功能。现在，看来模块化操作系统的某些关键功能“很快就会出现在设备上”。
在Windows10 Build 20185中，Microsoft添加了一个新面板，您可以在其中插入表情符号，GIF甚至剪贴板内容。全新的表情符号或剪贴板面板具有多项新功能，并且经过重新设计以提供更好的体验。
有一个新的主页，您可以在其中访问最近使用过的表情符号和GIF。您还可以搜索表情符号和GIF，这是Windows10上表情符号面板的新增功能。
Windows10的新面板将使您可以访问Symbol和kaomoji。表情符号面板还集成了一个称为“剪贴板历史记录”的功能，该功能使您可以查看最近复制到剪贴板的项目列表。
这个新的剪贴板历史记录支持文本，图像，HTML内容，并且可以在您的设备之间进行同步。您也可以删除剪贴板的历史记录或从“设置”中关闭该功能。
当前，剪贴板历史记录最多可存储25个条目，最早的条目将随着新条目的出现而消失。
Windows10通过此表情符号面板将剪贴板和表情符号体验提升到另一个层次，该功能预计将在下一个功能更新中出现。
Windows10的Windows 10 X功能
除了表情符号面板外，谣言还暗示Windows10也将具有更快的Windows Update体验，这可能意味着Windows10上的某些更新将立即安装。
Windows10也有望获得新的Action Center，重点关注生产力和简化的体验。
目前，尚不清楚这些功能何时在Windows10上首次亮相。
关于EKOffers促销微软软件：可1折买下Windows 10 Pro和微软商店促销的问题就给大家分享到这里，感谢你花时间阅读本站内容，更多关于Kube-Proxy-Windows CrashLoopBackOff 主节点Windows 工作节点、Microsoft shows off how containerized apps will work in Windows 10X、Microsoft: This is how Windows 10 has been changed by Windows Insider feedback、Microsoft现在向Windows10添加Windows 10X功能等相关知识的信息别忘了在本站进行查找喔。
本文标签：
