Pinned post
Google and OpenAI's AI product announcements over the past month have transformed the state of AI and show the breadth and pace of change (Ethan Mollick/One Useful Thing)
Ethan Mollick / One Useful Thing : Google and OpenAI's AI product announcements over the past month have transformed the state of AI ...
31 March 2023
Cybersecurity experts argue that pausing GPT-4 development is pointless - 2023-03-31 22:33:22Z
I was wrong — E3 is dead | Kaser Focus - 2023-03-31 23:07:45Z
Xbox Games with Gold users get Peaky Blinders game in April - 2023-03-31 20:13:21Z
The evolution of Web3 and the year crypto got serious - 2023-03-31 20:07:00Z
21 devs and creators help make a game with 8-year-old Roblox creator - 2023-03-31 18:00:00Z
Automation does not mean elimination: AI’s role in job security - 2023-03-31 18:07:00Z
Memories of E3 and moments of video game history | The DeanBeat - 2023-03-31 17:00:00Z
Working in cybersecurity and zero trust with Ericom Software’s David Canellos - 2023-03-31 16:50:08Z
How better use of data can improve compliance programs - 2023-03-31 17:07:00Z
Italy blocks ChatGPT, citing data privacy concerns, as calls for AI regulation grow - 2023-03-31 15:11:49Z
Announcing our judges for GamesBeat Visionary Awards - 2023-03-31 13:30:00Z
Detect whether Windows PE is booted in BIOS or UEFI mode
Check the HKLM\System\CurrentControlSet\Control\PEFirmwareType registry value to see if the PC is booted to UEFI or BIOS mode. Note: you may need to run wpeutil UpdateBootInfo to make sure this value is present.
reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType
This command returns 0x1 if the PC is booted into BIOS mode, or 0x2 if the PC is booted in UEFI mode.
wpeutil UpdateBootInfo for /f "tokens=2* delims= " %%A in ('reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType') DO SET Firmware=%%B :: Note: delims is a TAB followed by a space. if %Firmware%==0x1 echo The PC is booted in BIOS mode. if %Firmware%==0x2 echo The PC is booted in UEFI mode.
FW: Tweet by Clandestine on Twitter
| ||||||||||||||||||||||||
|
| | ||||||||||||||||||||||
|
FW: Tweet by Guy Leech on Twitter
| ||||||||||||||||||||||||
|
| | ||||||||||||||||||||||
|
FW: Tweet by David Brook - EUC365 on Twitter
| ||||||||||||||||||||||||
|
| | ||||||||||||||||||||||
|
30 March 2023
E3 2023 is canceled - 2023-03-30 20:42:08Z
The role missing from the tech company C-suite - 2023-03-30 20:07:00Z
Mastercard and Xsolla partner to enhance gameplay with payment technology - 2023-03-30 19:10:00Z
Diablo IV Beta sets franchise record, 61.5 million hours played - 2023-03-30 19:36:46Z
Beat Saber updates its Panic! At The Disco pack with six new songs - 2023-03-30 19:07:36Z
5 ways machine learning must evolve in a difficult 2023 - 2023-03-30 18:07:00Z
Got It AI’s ELMAR challenges GPT-4 and LLaMa, scores well on hallucination benchmarks - 2023-03-30 16:09:22Z
4 key things IoT developers need to keep in mind as the number of connected devices explodes - 2023-03-30 17:07:00Z
Berkeley SkyDeck sees 120% increase in applicants and chooses 18 final startups - 2023-03-30 15:00:00Z
Active blockchain wallets drop 9.7% compared to previous quarter | DappRadar - 2023-03-30 15:00:00Z
Xsolla announces its new telecommunications initiative plus a new cloud solution at GDC - 2023-03-30 13:20:00Z
OpenAI’s GPT-4 violates FTC rules, argues AI policy group - 2023-03-30 14:30:00Z
Skillprint launches science-backed platform to match players with the right skill-based games - 2023-03-30 13:00:00Z
DataDome raises $42M to leverage machine learning for confronting bot attacks - 2023-03-30 13:00:00Z
Rogue Games will launch Hello Kitty dance game for Switch on April 13 - 2023-03-30 13:00:00Z
MariaDB debuts new SkySQL features to help teams manage cloud costs - 2023-03-30 12:00:00Z
Securing cloud tech stacks with zero trust will drive growth of confidential computing - 2023-03-30 12:12:00Z
Sky Mavis brings 4 new blockchain games to its Ronin network - 2023-03-30 10:00:00Z
Keywords acquires Digital Media Management to move into social and online marketing - 2023-03-30 06:30:00Z
EA will lay off 6% of its staff to drive greater focus in uncertain economy - 2023-03-29 23:55:00Z
29 March 2023
Hogwarts Legacy beats Call of Duty | Circana February 2023 - 2023-03-29 21:35:43Z
Mobile game market stabilizes above pre-pandemic levels | Data AI - 2023-03-29 23:04:22Z
To create a more accessible internet, context matters - 2023-03-29 20:07:00Z
Autonomous agents and decentralized ML on tap as Fetch AI raises $40M - 2023-03-29 20:23:22Z
PS Plus gets Meet Your Maker and Sackboy in April - 2023-03-29 19:35:21Z
How to use AI to improve customer service and drive long-term business growth - 2023-03-29 18:07:00Z
Open letter calling for AI ‘pause’ shines light on fierce debate around risks vs. hype - 2023-03-29 16:42:55Z
Why exams intended for humans might not be good benchmarks for LLMs like GPT-4 - 2023-03-29 16:07:00Z
How Epic Games views the metaverse and the State of Unreal | Tim Sweeney - 2023-03-29 14:30:00Z
Google advances AlloyDB, BigQuery at Data Cloud and AI Summit - 2023-03-29 13:00:00Z
Open source Kubeflow 1.7 set to ‘transform’ MLops - 2023-03-29 13:00:00Z
Sybo CEO believes gaming can foster social change and empathy | Mathias Nørvig - 2023-03-29 13:30:00Z
Modify WINRE on a running PC
You can modify
the Windows Recovery image on a running PC. The following steps walk you
through mounting a Windows Recovery image, applying an update to it, and then
saving the changes:
1. Open a Command Prompt as
administrator.
2. Create a directory where you can
mount the recovery image to make changes to it.
Windows Command Prompt
md c:\mount
3. Mount your recovery image
with REAgentC:
Windows Command Prompt
ReAgentC.exe
/mountre /path c:\mount
4. With your recovery image mounted,
you can download and add the update package to the Windows RE image.
Windows Command Prompt
Dism /Add-Package
/Image:C:\mount\ /PackagePath:"c:\downloadedupdate\update.msu"
or
Windows Command Prompt
Dism /Add-Package
/Image:C:\mount\ /PackagePath:"c:\downloadedupdate\dynamicupdate.cab"
5. If you added a Dynamic Update
package, validate that the package you added is in your image:
Windows Command Prompt
Dism /Image:C:\mount\ /Get-Packages
Check the list for the update package you just
added. The package should include the KB number, and will show the State as Installed if it's been successfully
added:
Package Identity :
Package_for_KB5021041~31bf3856ad364e35~amd64~~22621.815.1.0
State : Installed
Release Type :
Update
6. Clean up your recovery image and
reset the base of any superseded components:
Windows Command Prompt
dism
/image:C:\mount /cleanup-image /StartComponentCleanup /ResetBase
7. Unmount the Windows recovery
image:
Windows Command Prompt
ReAgentC.exe
/unmountre /path c:\mount /commit
8. If the PC's disk is protected by
BitLocker or Device Encryption: Use ReagentC to disable and then
re-enable Windows RE. This ensures that the updated Windows RE image is turned
on and correctly configured for your Windows installation:
Windows Command Prompt
reagentc /disable
reagentc /enable
The
Windows RE image on the running PC is now updated.
Check the WinRE image version
You can
check the WinRE image's version number on both online and offline Windows
installations. This can be helpful for checking the WinRE version prior to
adding an update, and then after applying an update to verify that the update
was successfully added.
Note
The WinRE
version number will only change after you add an LCU. If you add a DU package,
use DISM /get-packages as described in the steps above to ensure that the
package has been added to the image.
Validate the Windows RE version
in an Online Windows OS
1. Use ReagentC to find the location of the
installed WinRE image by running the following command:
Windows Command Prompt
reagentc /info
This command returns the Windows RE location that
resembles the following example:
Windows Command Prompt
\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
2. Use DISM to get version
information about the winre.wim image located in the path returned by ReagentC
in the previous step. Make sure to add the WinRE image name and image index
number to the path when you run the command:
Windows Command Prompt
Dism /Get-ImageInfo
/ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim
/index:1
Notice the reported version. For example:
Windows Command Prompt
Version : 10.0.22621
ServicePack Build :
1
ServicePack Level :
0
Make sure that the ServicePackBuild is greater than or equal to
the UBR for the update that you added. For example, for Windows 11, version
22H2, the November security update would show 819 as the SerivcePack
Build, since
full version number for that update is 22621.819.
·
If the
version reported is an earlier version, this indicates the Windows RE image is
not up to date.
·
If the
reported version is the same or a later version, no action is needed.
Validate the Windows RE version
in an Offline Windows OS
1. Mount the Windows image to a local folder,
for example C:\mount\windows:
Windows Command Prompt
mkdir C:\mount\windows
Dism /Mount-Image
/ImageFile:C:\mount\install.wim /Index:1
/MountDir:C:\mount\windows
2. Use DISM to get version
information about the winre.wim image located in the Windows\system32\recovery folder. Make sure to
specify the image's index number when you run the command:
Windows Command Prompt
Dism /Get-ImageInfo
/ImageFile:c:\mount\windows\windows\system32\recovery\winre.wim /index:1
Notice the reported version. For example:
Windows Command Prompt
Version : 10.0.22621
ServicePack Build :
1
ServicePack Level :
0
Make sure that the ServicePackBuild is greater than or equal to
the UBR for the update that you added. For example, for Windows 11, version
22H2, the November security update would show 819 as the SerivcePack
Build, since
full version number for that update is 22621.819.
·
If the
reported version is an earlier version, this indicates the Windows RE image is
not up to date.
·
If the
reported version is the same or a later version, no action is needed.