Any VPCZ1 owners who are trying to install Windows 11?

I understand that our model don't meet the min requirements, such as TPM 2.0, old 1st gen CPU, secureboot... but there are ways to bypass this fortunately.

Anyone planning on taking this journey for experimentation?

BTW, my VPCZ1 is still holding... a new keyboard is on the way as I speak.

 

Yes, I'll go for it. Might take me a few days though.
I believe the way to go is to use a Win10 ISO and replace the install.wim with the install.wim from the Win11 ISO.

Not sure if the UEFI requirement will cause issues or not.

 

Did an in place upgrade (from Windows 10) using a Windows 10 iso after replacing appraiserres.dll from a Windows 10 iso to get around the hardware requirements issue.
Everything went fine. There were three unknown devices in the device manager. Windows update gave me drivers for two. Had to dig out my old drivers saved on an external HDD to find the SFEP driver. If anyone wants it I can upload for them - I wasn't able to find it on the internet.

Note: I have a hacked BIOS - static switching. So far I have not done anything for the nVIDIA GPU.

Next I'll try clean installing from the USB stick I made from the iso.

 

A clean install gave me 4 problem devices in Device Manager.
1. Intel graphics driver - got from WU-> optional updates.
2. Authen-Tec fingerprint reader driver - got from WU-> optional updates.
3. Base system device - Ricoh MS card reader and SD card reader (drivers from my backup on an external HDD)
4. Unknown device - SFEP (driver from my backup on an external HDD)

Windows 11 REALLY wants you to use a Microsoft account. A lot of stuff (even widgets) don't work without it.

 

nVIDIA GT330M Patched 342.01 driver working fine on Windows 11 Pro x64 22000.51.
(Note: I have a hacked BIOS with static switching, not the hybrid system).
Everything seems to be working just fine - damn M$ and their artificial and arbitrary hardware requirements and exclusions.
I haven't tested it thoroughly - this is a 11 year old laptop and the cooling system is shot, so running in speed mode (with discrete graphics) results in the laptop overheating and turning off. I'll have a go at doing some maintenance, but I'll probably have better luck in winter when it gets cooler.

 

Very nice! Thanks for going through all the trouble and getting back to me. Glad to hear that the workaround works OK for our devices! As for the SFEP driver goes, it should work with the one that worked with Windows 10 right?

I was digging through some older threads about the TPM, and if I recall correctly, the US model does not come with the TPM, while other models do. Hopefully MS doesn't block the workaround in the official release.

 

Just run the tool shown in my screenshot. It will tell you what are the points of contention. WhyNotWin11.exe - get it from github.
Yes, whatever drivers worked in Windows 20 are working in Windows 11. Windows Update gives you everything except SFEP and the Ricoh card reader drivers, and, of course, the modded nVIDIA driver.

I expect the hardware restrictions will eventually come down to the feature level - as it should have been from the get go (what were you thinking, Microsoft?).
A feature that depends on specific hardware will not work if that hardware isn't there. Touch input needs a touch screen, Windows Hello face login needs a supported webcam, newer processors for the Android subsystem, ... that kind of thing.

 

So what's definitely not working at this time is the Widgets pane when the Intel graphics is selected. The widgets pane is completely blank - a rather nice translucent pane. The widgets are there, though - just invisible. Hovering over various portions changes the cursor to a hand, shows a tooltip, and clicking there launches Edge and opens the correct link.
Widgets work fine with the NVIDIA graphics adapter, though.
You can force the Widgets to work with the Intel graphics by going to device manager and disabling the Intel graphics adapter. Widgets will start working. Now you can re-enable the Intel graphics adapter and the widgets will continue to work, but only until the next reboot.

 

That’s so strange. I’m mostly going to stay in SPEED mode so hopefully that won’t be an issue then. Nevertheless thanks for the warning!

One question I have is, once you have installed the Windows 11 on this device, are you able to keep receiving updates? And when you do, does it throw you any errors? Caused by incompatibility or anything like that? Thanks!

 

Windows 11 is not released to the general public; you have to be in the Windows Insider Programme and in the developer channel. Just this week it has been released to the beta channel. Fortunately for us, the guys at mydigitallife have made a script which enrolls you into the desired channel in the insider programme. All updates work, both for Windows and for Microsoft store, which is where you get updates for your apps.

I'm seeing some battery related weirdness, but my battery is a compatible replacement, so I can't really complain. Starts off at 0%, charges slowly to about 35%, then suddenly shows 100%. Discharges normally to about 50%, then suddenly says battery is about to run out, shows about 10%, and then goes into hibernation. Perhaps it is different for a genuine battery.

 

As of 22000.132, the widgets pane is working fine on Intel graphics.

 

I have been a long-time VAIO/SONY supporter for many many years, but I am unfortunate to say the quality of their products is falling over the years .

 

Sony sold off the laptop business and the VAIO brand. The new owners are just getting started.

 

In fact I think SONY would be wise to buy them back now, as it shows laptops aren't going to dissappear.
And people are looking for quality products with higher lifespans. My Z is the oldest electronical product in my household and still going strong

Sent from my BLA-L29 using Tapatalk

 

what about with newer W11 builds like 22000.318 & 22000.348?
btw, MS did silently release updated Win11 ISOs on the Win11 download page in mid-Nov 2021 that contain build 22000.318 instead of 22000.194.

seems Win11 is more stable now (with at least .318) than with previous builds

 

22000.318 needed this new little fix. And more will come. Microsoft should never ever pushed out Win 11 in this state before proper testing. But they had to because they was ready to throw out their own small Surface Jokebooks.

Improvements and fixes
This non-security update includes quality improvements. Key changes include:

• Addresses an issue that affects the Appx PowerShell cmdlet functionality on PowerShell 7.1 and later.
  
  
• Addresses an issue that causes some users to see an unexpected “bad image” error message dialog at startup.
  
  
• Addresses an issue that causes searchindexer.exe to stop responding during a dismount operation in the remote desktop environment.
  
  
• Addresses an issue that affects the opening of the SearchFilterHost.exe process.
  
  
• Adds support for the cancellation of daylight savings time for the Republic of Fiji for 2021.
  
  
• Addresses an issue that causes devices that have certain processors to stop responding when waking from hibernation.
  
  
• Addresses a COM initialization issue in wslapi.dll that might cause the calling process to stop working.
  
  
• Addresses an issue in the Hyper-V virtual machine bus (VMBus) that causes the Windows Subsystem for Linux (WSL) VM to occasionally time out when attaching disks. This issue also prevents the utility from starting.
  
  
• Addresses an issue that affects the System Memory Management Unit’s (SMMU) fault handling after hibernation.
  
  
• Addresses an issue that causes the system to stop working after you enable Hyper-V.
  
  
• Addresses an issue that fails to apply machine Group Policy objects automatically at startup or in the background to devices on a domain that have certain processors.
  
  
• Addresses an issue that causes the Server Manager cmdlet to return a failure. As a result, many Software Defined Data Center (SDDC) validations fail during the installation of optional features.
  
  
• Adds the option to configure an Internet Protocol version 4 (IPv4) maximum transmission unit (MTU) that is less than 576 bytes on an interface.
  
  
• Addresses an issue that causes get-winevent to fail, and the error is an InvalidOperationException.
  
  
• Addresses an issue that incorrectly renders some variable fonts.
  
  
• Addresses an issue that displays glyphs at the wrong angle when you use the Meiryo UI font and other vertical fonts. These fonts are frequently used in Japan, China, or other countries in Asia.
  
  
• Adds a feature to facilitate certain cross-browser data transfers.
  
  
• Addresses an issue that occurs when a dialog opens within Internet Explorer.
  
  
• Addresses an issue that affects Internet Explorer COM automation scenarios. For more information, see Internet Explorer 11 desktop app retirement FAQ.
  
  
• Addresses an issue that causes Internet Explorer to stop working when you copy and paste text while using the Input Method Editor (IME).
  
  
• Addresses an issue that causes certain apps to stop responding to input. This issue occurs on devices that have a touchpad.
  
  
• Addresses a touch keyboard deployment issue that affects WebView2 controls in Windows UI Library 3.0 (WinUI 3) applications.
  
  
• Addresses a memory leak in ctfmon.exe that occurs when you switch between different edit clients.
  
  
• Updates the phone number for Windows Activation for locales that have the wrong phone number.
  
  
• Addresses a known issue that causes error codes 0x000006e4, 0x0000007c, or 0x00000709 when connecting to a remote printer that is shared on a Windows print server.
  
  
• Addresses an issue that affects USB Print devices that support Internet Printing Protocol (IPP) Over USB. This issue prevents these USB Print devices from completing installation.
  
  
• Addresses an issue that causes certain USB Print installers to report that they don’t detect the printer after you plug it in.
  
  
• Addresses an issue that might improperly redirect OS functionality when you invoke microsoft-edge: links.
  
  
• Addresses an issue in the Windows audio system that might cause the audiodg.exe process to stop working, which results in a temporary loss of audio.
  
  
• Addresses an issue that prevents Software-Defined Networking (SDN) virtual machines from working when you configure the Generic Routing Encapsulation (GRE) VPN bandwidth limitation.
  
  
• Addresses an issue that might cause the return value of GetCommandLineA() to be lowercase in some developer scenarios.
  
  
• Addresses a Primary Refresh Token (PRT) update issue that occurs when VPN users sign in using Windows Hello for Business when the VPN connection is offline. Users receive unexpected authentication prompts for online resources that are configured for user sign-in frequency (SIF) in Azure Active Directory-Conditional Access.
  
  
• Adds the message that indicates that an organization's policy manages the user's location privacy settings. This message appears when the privacy settings are controlled by the Group Policy documented in Manage connections from Windows 10 and Windows 11 operating system components to Microsoft services.
  
  
• Addresses an issue that affects the Fast Identity Online 2.0 (FIDO2) credential provider and prevents the display of the PIN entry box.
  
  
• Addresses an issue that causes Windows Defender Application Control to incorrectly compare two file version numbers.
  
  
• Enhances Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks.
  
  
• Addresses an issue that might cause Windows Mixed Reality to start when you put on a headset. This issue occurs even when you’ve turned off the option “Start Mixed Reality Portal when my headset's presence sensor detects that I'm wearing it”.
  
  
• Addresses an audio distortion issue that affects Xbox One and Xbox Series Audio peripherals and occurs when you use them with spatial audio.
  
  
• Addresses an issue that causes the AltGr key to stop working if a remote desktop client is running or if RemoteApp was disconnected.
  
  
• Addresses an issue that causes the edit button and the battery icon in Quick Settings to intermittently disappear.
  
  
• Addresses an issue that affects the Focus Assist button in the notification area, and this update provides an accessible name for screen readers.
  
  
• Updates several aspects of Windows emoji. As part of an iterative and ongoing work, we have made the following improvements for this release:
  • Updates all emoji from the Segoe UI Emoji font to the Fluent 2D emoji style
    
    
  • Includes support for Emoji 13.1, which:
    • Updates the emoji dictionary
      
      
    • Adds the ability to search for Emoji 13.1 in all supported languages
      
      
    • Updates the Emoji and more panel so you can enter emoji in your applications
• Addresses an issue that affects the display of the number of unread notifications; some numbers don’t appear in the center of the circle in the notification area.
  
  
• Addresses an issue that affects the Start menu when you install a large number of apps and change the screen resolution. The app names appear on the Start menu, but the app icons are missing. This update might also improve the reliability of the Start menu when you use secondary monitors in mixed resolution scenarios.
  
  
• Addresses an issue that causes flickering when you hover over icons on the taskbar; this issue occurs if you’ve applied a high contrast theme.
  
  
• Addresses an issue that, under certain conditions, prevents the keyboard focus rectangle from being visible when you use Task View, Alt-Tab, or Snap Assist.
  
  
• Addresses an issue that affects apps that provide context (shortcut) menu items in File Explorer and desktop context menus. This issue occurs if these apps utilize Directory or Directory\Background registrations. .
  
  
• Addresses an issue that automatically removes the Serbian (Latin) Windows display language from a device.
  
  
• Addresses an issue that displays the incorrect background for the iFLY Simplified Chinese IME icon in the notification area.
  
  
• Addresses an issue that displays a blank space on the bottom of the Touch keyboard when you close the keyboard while the Suggestion UI is expanded.
  
  
• Addresses reliability issues that prevent the display of File Explorer and desktop shortcut menus. This issue often occurs when you choose to use a single click to open an item.
  
  
• Adds an option for you to choose whether to automatically turn on Focus Assist for the first hour after a Windows feature update.
  
  
• Improves the animation performance of icons on the taskbar.
  
  
• Addresses volume control issues that affect Bluetooth audio devices.
  
  
• Addresses an issue that causes File Explorer to stop working after you close a File Explorer window.
  
  
• Addresses an issue that displays incorrect closed-caption shadows for some videos.
  
  
• Addresses an issue that occurs when you run a 32-bit application on a 64-bit version of Windows 11. If you call NetServerEnum(), it might return error 87 or error 1231.
  
  
• Addresses an issue that prevents your device from starting up, and it becomes unresponsive because of licensing API calls.
  
  
• Addresses an issue that prevents flash drives, such SD cards and certain USB drives, from appearing in the Defragment and Optimize Drives UI.
  
  
• Addresses an issue that affects NTFS when you enable the update sequence number (USN) journal. NTFS performs unnecessary actions each time it performs a write operation, which affects I/O performance.
  
  
• Enables onunload events to create pop-up windows in Microsoft Edge Internet Explorer mode.
  
  
• Updates the Start menu's Ease of Access folder name to “Accessibility” to match our naming standard across Windows 11 (original release).
  
  
• Addresses an issue that affects Microsoft Narrator users when they select Braille options in Settings.
  
  
• Changes the screen color to blue when a device stops working or a stop error occurs as in previous versions of Windows.
  
  
• Addresses an issue that causes some app icons in the Start's All apps list to be cut off on the bottom after you change the screen resolution.
  
  
• Addresses a reliability issue on the lock screen that affects the rendering of the network status text.
  
  
• Addresses an issue that causes the Windows Update History page in the Settings app to display a summary count of zero (0) updates per category when there are updates listed.
  
  
• Addresses an issue in the Windows Network File System (NFS) client that might prevent you from renaming a file after mounting an NFS share. This issue occurs if you rename the file using File Explorer, but does not occur if you rename the file using command line.
  
  
• Addresses an issue that might cause a stop error in volmgr.sys when you delete a volume.
  
  
• Addresses a known issue that might prevent apps, such as Kaspersky apps, from opening after you attempt to repair or update the apps using the Microsoft Installer (MSI).

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.