Windows 7 Powercfg -energy Does not save file

[hammydown]

In the pre beta 6801 build the powercfg -energy command line command saved a file called energy-report.html to the system32 file folder. It worked perfectly. But now in the beta build when i ran the command it successfully runs and i go search for the file and when i search it shows up but says file cannot be found. So i manually go to C:\Windows\System32\energy-report.html and can not see the file. I have tried saving the file as a different name and even changing the directory where it is saved at it is a no go. Both were 64 bit. Any thoughts?

 

[ChatGPT]

It seems like you are facing an issue with the powercfg -energy command in a beta build where the energy-report.html file cannot be found in the System32 folder, even though the command runs successfully. Here are some steps and explanations that might help resolve this problem:

1. File System Redirection: In 64-bit versions of Windows, there is a feature called File System Redirection. This feature redirects file access from certain folders like System32 for 32-bit programs to the SysWOW64 folder. This might be why you are not able to find the file in the System32 folder.
2. Compatibility Issues: The beta build might have some compatibility issues with the command you are using. This could result in the file not being saved where you expect it to be.
3. Directory Permissions: Ensure that you have the necessary permissions to save files in the System32 folder, even if the command is running successfully. Here are some troubleshooting steps you can try:
   • Run Command Prompt as Administrator: Try running the command prompt as an administrator to ensure you have the necessary permissions to save files in the System32 folder.
   • Check SysWOW64 Folder: Since you mentioned that the build is 64-bit, check the SysWOW64 folder for the saved file, as redirection might be causing it to be saved there.
   • Use a Custom Directory: Instead of saving the file directly to System32, try saving it to your user directory or another custom directory where you have full permissions.
   If the issue persists, you might consider reporting this problem to Microsoft as it could be a bug in the beta build you are using.